As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
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.
Hi,
and here lof from CMD windows
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?
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.
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).
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:
server.log
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.
/etc/init.d/nuxeo start
I'm not sure you have the same issue if it only occurs when adding a bundle, please fill a dedicated question for yours.
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, ...).
PID
startbg
restartbg
You can also follow http://doc.nuxeo.com/x/eABu in order to check if the process ID is retrievable or not.
Bump!<br/>Did you get the solution from one of the following answers or by yourselves? If so, please mark it as accepted or share your own.<br/>Thanks
Hello Dear:
I found the solution to the problem generated by the aforementioned error message.
What I have done has been as follows:
In nuxeo.conf file located in C:\ProgramData\Nuxeo\Conf\ in the line corresponding to
C:\ProgramData\Nuxeo\Conf\
JAVA_OPTS=-Xms512m -Xmx1024m -XX:MaxPermSize=512m I set the values ??in half and EUREKA! this has worked wonders!
JAVA_OPTS=-Xms512m -Xmx1024m -XX:MaxPermSize=512m
Then, the content should look like:
JAVA_OPTS=-Xms256m -Xmx512m -XX:MaxPermSize=256m.
JAVA_OPTS=-Xms256m -Xmx512m -XX:MaxPermSize=256m
As a precaution, I have also made ??this change to the same values ??in the following files in C:\Nuxeo\bin:
C:\Nuxeo\bin
Bon voyage!
Thanks for the feedback.
Dear Julien Carsique
Yes
when i got this message, what i do is to close the browser, run nuxeo and then nuxeo got the process.
it´s simple, but it works for me
