I drove to the data center yesterday. The machine didn't even shutdown. All fans running, memory okay...Okay, no hardware issue after all. In fact, it was a broken maintenance script which was supposed to set up the chroot environment for postfix. Instead, it copied everything to the root directory and changed the permission of /tmp to 755 and ownership to user "postfix". Thus, a couple of processes just crashed. At least the machine continued to process incoming e-mail. Well, almost exclusively.
After implementing a workaround for the bug (still need to do the analysis what exactly causes this), and fixing the broken permissions, the machine came up cleanly again.
I dropped the plan to move to OX6, mainly for three reasons: the new AJAX-driven user interface has a far too complex layout and has a terrible usability. Second, even setting up the thing with the sparse available documentation is a nightmare. And third, it is buggy as hell: the webmail interface shows just one message (and logs errors about out of sequence responses. Um, yes, but IMAP is supposed to do that...) The groupware server didn't come up after the crash, without any error message.
No way I'm going to administrate that horrible mess. I'm back at Horde IMP now. I have some minor issues with that one as well, but at least nothing unsolvable. The worst one are missing sequences in the database. Horde complains about relations horde_datatree_seq, horde_histories_seq, jonah_channels_seq, jonah_stories_seq, kronolith_shares_seq and
rean_bookmarks_seq missing. It is an FAQ, in fact. But it isn't really helpful to find twenty responses by one of the main horde developers that this is bug in the MDB2 pear module and one should complain to them. Just that, no information what exactly is wrong here.
Here are some pointers: if you are running MySQL, check whether the user "horde" has the permissions to create tables in database "horde". Also, pear-mdb2 seems to have issues with certain MySQL versions. Up- or downgrade MySQL in that case. If this doesn't help either, create the tables manually. However. I'm using Postgresql. The current version of MDB2 just does not create the sequences. They have to be created manually with "CREATE SEQUENCE horde_datatree_seq;" It took me half a day to find that, as I do not know anything about SQL.
And just as I was about to migrate the user data to Horde, my DSL modem broke. Not completely unexpected (it was one of the few remaining modems of that series still in use), but my only connection right now is via ISDN.
Comments
lynard-.livejournal.com 15 years, 9 months ago
Weia, wenn's dicke kommt dann gleich richtig, oder?
Link | Replyzefirodragon.livejournal.com 15 years, 9 months ago
That's quite an interesting case :)
And I SOOO know how it is to hunt down the internet for one little line of information, like your SQL statement here.
Link | ReplyNew Comment