Jared Ready
2013-10-09 15:03:09 UTC
Jared Ready [http://community.zenoss.org/people/residentbiscuit] created the discussion
"4.2.x has been extremely buggy for us"
To view the discussion, visit: http://community.zenoss.org/message/74888#74888
--------------------------------------------------------------
Since our install of 4.2.3 (now 4.2.4), we have had a terrible time. I spend at least a full day of work each week just trying to maintain this install and keep it running. We have daemons dying multiple times a week for seemingly no reason (zenmodeler and zenperfsnmp). Our data polling just quits all the time, so now we have these lovely gaps in all of our graphs, which makes them near useless for determining historical trends. The zenjobs daemon has been refusing to work for the last week now, so we can no longer add/move devices without hard killing the zenjobs processes first. The UI performance has been significantly slower than it was in 3.x, sometimes it appears to be completely unresponsive.
Zenoss has always had it's little bugs, as will any piece of software this size. But this latest 4.x release has just been almost unusable for us. We have been considering just reverting back to a 3.2.1 install where we know the core functionality of the system worked without major issues, not to mention we could go back to having a responsive UI.
We run Zenoss core 4.2.4 on a RHEL6 VM with 16GB RAM and 8 cores, one collector. We monitor 693 devices.
Our upgrade process was as follows:
Our 3.2.1 install was sitting on a physical RHEL5 box, and we wanted to upgrade up to RHEL6 as well.
We created a fresh RHEL6 VM, installed Zenoss 3.2.1 using Shane Scott's modified RPM.
We then migrated our Data.fs and $ZENHOME/etc from the RHEL5 box to the new RHEL6 box.
From here we upgraded Zenoss up to 4.2.3. <-- Issues started pretty soon after this.
We then upgraded up to 4.2.4.
</rant>
Has anyone else been having as many issues as us, or am I alone with this?
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74888#74888]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"4.2.x has been extremely buggy for us"
To view the discussion, visit: http://community.zenoss.org/message/74888#74888
--------------------------------------------------------------
Since our install of 4.2.3 (now 4.2.4), we have had a terrible time. I spend at least a full day of work each week just trying to maintain this install and keep it running. We have daemons dying multiple times a week for seemingly no reason (zenmodeler and zenperfsnmp). Our data polling just quits all the time, so now we have these lovely gaps in all of our graphs, which makes them near useless for determining historical trends. The zenjobs daemon has been refusing to work for the last week now, so we can no longer add/move devices without hard killing the zenjobs processes first. The UI performance has been significantly slower than it was in 3.x, sometimes it appears to be completely unresponsive.
Zenoss has always had it's little bugs, as will any piece of software this size. But this latest 4.x release has just been almost unusable for us. We have been considering just reverting back to a 3.2.1 install where we know the core functionality of the system worked without major issues, not to mention we could go back to having a responsive UI.
We run Zenoss core 4.2.4 on a RHEL6 VM with 16GB RAM and 8 cores, one collector. We monitor 693 devices.
Our upgrade process was as follows:
Our 3.2.1 install was sitting on a physical RHEL5 box, and we wanted to upgrade up to RHEL6 as well.
We created a fresh RHEL6 VM, installed Zenoss 3.2.1 using Shane Scott's modified RPM.
We then migrated our Data.fs and $ZENHOME/etc from the RHEL5 box to the new RHEL6 box.
From here we upgraded Zenoss up to 4.2.3. <-- Issues started pretty soon after this.
We then upgraded up to 4.2.4.
</rant>
Has anyone else been having as many issues as us, or am I alone with this?
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74888#74888]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]