05-29-2012 11:29 AM
Hello,
After restarting the server. nuxeo unbootable, I have the error messages: Sent start command server object Could not get process ID.
Thank you for your feedback.
05-29-2012 01:43 PM
Hi,
05-29-2012 01:50 PM
Hello,
05-29-2012 01:56 PM
and here lof from CMD windows
05-30-2012 01:52 PM
I've got the same error and I don't understand why... This http://doc.nuxeo.com/display/KB/Launcher+says+it+couldn%27t+retrieve+process+ID is useless for me, but maybe can it help you?
05-30-2012 02:13 PM
Hi, I don't have the technical answer, however I updated your question title to make it more understandable for others. Hopefully, some more tech. persons will help you.
05-30-2012 06:48 PM
I noticed your install files are on the F: drive. I have run into problems on Windows when not installing to C:. See the following link for additional information (http://answers.nuxeo.com/questions/532/force-install-to-use-drive-other-than-c-for-all-components).
05-31-2012 05:44 AM
I have the same problem. The server stops but does not start again.
This problem only occurs if I do this after installing a new JAR archive:
cp xyz.jar /var/lib/nuxeo/server/nxserver/bundles/
/etc/init.d/nuxeo restart
So I think this is a problem with the handling of the archives and some sort of time out (or state management).
The content of server.log
is the following:
2012-05-31 09:39:49,726 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
2012-05-31 09:39:49,726 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
2012-05-31 09:39:49,726 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
I don't know if this exactly the same problem but if I run /etc/init.d/nuxeo start
again then the server starts normally.
06-05-2012 11:11 AM
I'm not sure you have the same issue if it only occurs when adding a bundle, please fill a dedicated question for yours.
06-05-2012 11:18 AM
Shutdown happens 1h after the startup. Are you sure the server wasn't started?
Which command did you run to start the server? What is your OS version? On some Windows versions, it is not possible for the Nuxeo launcher to retrieve the process ID (aka PID
) so a workaround is to start Nuxeo in background (see nuxeoctl commands such as startbg
, restartbg
, ...).
You can also follow http://doc.nuxeo.com/x/eABu in order to check if the process ID is retrievable or not.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.