I’m really new here, so i’m sorry if i post to the wrong place, but we really need some help.
We are using interworx for a half year now without any problems. Today, from 3 AM, one of our machines started an update via yum, and it got stuck. Half hour ago, i tried to reboot the server, but the problem stayed, we cannot reach nodeworx nor siteworx. The websites are running, and we can log in via SSH, but we dont know what to do.
And i cant ask for support via nodeworx, thats why i wrote here.
Emmosystems PM me, and actually rereading his post, it shows updating stalled and server restarted, so the current condition of nodeworx is showing maintenance webpage.
I would ssh into server with root permissions (su or root) and run yum update iworx or yum update and allow server to fully complete on update.
If it fails on some updates, I would post the failures but I’m thinking it is just the restart of server breaking the update process
Then restart server (belts and braces to clear down server) and test
Emmosystems, I’ll pm you now but I do not work for interworx sorry.
Also, IW support are in USA time zone, so hopefully at this time of day here in uk, should not be long hopefully
I’ve got the same problem on two servers. Restarting iworx service results in “Binding IP Aliases:[FAILED]”, running yum update iworx won’t help, s yum ist stuck: “Another app is currently holding the yum lock; waiting for it to exit… The other application is: yum”
We’re having the same issue this morning. Stuck in maintenance mode. Killed stuck yum processes, rebooted, recompleted the interworx yum update, but still stuck in maintenance mode. Not really sure what to do at this point.
I have the exact same situation as the others mentioned.
The only difference is, that we could complete the failed yum updates, everything is updated. cvspermsfix.pex failing cuz it cannod find the horde.log in the default log directory (possible because horde package just updated, and we never use it).
Two other servers updated just fine yesterday (version 5.1.3-1041), but since I can’t acces Nodeworx, I can’t confirm it’s the same update. The changelog unfortunately is out-of-date.
Problem persists. I just said that we could finish the failed update which causing the whole problem at our servers.
In our situation an update of iworx core started this morning 3 AM. We saw it at 9 AM. So we mentioned something failed. We finished yum transactions by killing and rerunning yum update , and then rebooted server twice. Now yum saying no update, but the problem persists, Maintenance mode. The hosted websites running tho, but we couldnt do any config in the nodeworx, and its starting to be a a bigger problem now cuz our customers needs modifications
It looks like there was an issue with the latest release candidate. The development team is still investigating the issue, but it appears that an rpm command was run during the yum update process, which hung since yum locked the rpm database. Please submit a support ticket with remote assistance and the server IP for all affected servers and we will finish the upgrade steps.
Apologies, you were correct with your first post in highlighting where the issue was, and when I updated our test server, saw the same and checked top, which showed db in use.
Hope your well and business is good, and once again, apologies it just seems to be one of those days for me