maybe im just a bit too blind but is there a way to restart the server from the admin console? i saw you can stop it but i want that it just restart…any help would be great…
p.s: i love jive…its a awsome simple jabber server. we run it here in our company
this was one of my suggestions in my first thread there:) There is no restart option in Admin Console and Launcher. So you must stop and then start server. If you are using Windows you can just restart JM service in services.msc or write some bat script using messenger-service.exe /stop
messenger-service.exe /start
commands
in Linux you can do almost the same with /bin/messenger stop and /bin/messenger start, but im just restarting my linux machine:) Well, i only need to restart server in testing phase so it’'s not really “must be” function:)
Because of the way the server is launched, it’‘s not currently possible for us to have a restart option in the admin console. We hope to add this in the future. For now, wroot’'s suggestions are probably the best way to go.
Regards,
Matt
thank you that with the script is a awsome idea…mostly we dont need to restart but when then its always some work all over vnc
i’'m using PuTTY+SSH:)
yes thats alot better but i just have here a win2k server but i would love to run this service on a linux machine. but hey at least it works except the windows downtime
Do you mean that you are not able to script a service restart?
Actually, when TLS certs are installed, there is a message to the effect that the server has to be restarted, with a link in it. If that link is clicked, then the server restarts. Are you able to replicate the same function on the main dashboard, but without the installation of the certs? I am confused and do not understand how the 2 would be different.
@bashkim, you are responding the a message that is nearly twenty years old.
Yes, I know that. It’s a shame that no one considered adding a button/link on the admin UI that can restart the server. There is a link to restart its HTTP part, so why not the XMPP part? For us admins it means having to remote into the host by other means, for that single task only, whereas we are already logged into the admin UI.
The webservice is restarted by reloading an embedded component. Restarting the XMPP part means stopping the entire process/application. That’s a different beast. Apart from that: a failure to restart the web server would be annoying, but would not affect most functionality by end-users. A failure in restarting the entire server is … worse. I’m dreading scenario’s where people fail to restart a server, and not have access to the underlying OS.
An admin is more than capable of taking that risk. Why the push-back?