Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: besterl on April 11, 2011, 04:11:44 PM

Title: Corrupted Perl
Post by: besterl on April 11, 2011, 04:11:44 PM: My mail stopped working after a power failure (and consequent fsck)

Qpsmtp log has a bunch of perl errors

Instead of just removing and reinstalling all perl modules - how can I check which ones is needed by qpsmtpd and just do them?

Thanks
Title: Re: Corrupted Perl
Post by: Stefano on April 11, 2011, 04:21:46 PM: what about telling us something about the errors?
Title: Re: Corrupted Perl
Post by: besterl on April 20, 2011, 01:17:13 PM: Hi - Sorry for the late reply

I just removed and reinstalled all the perl modules - and all is OK

I think some of them got corrupted due to successive power failures
Title: Re: Corrupted Perl
Post by: cactus on April 20, 2011, 07:27:49 PM: Quote from: besterl on April 20, 2011, 01:17:13 PM
I think some of them got corrupted due to successive power failures
If that is the case, that should have also happened to other data on the same disk IMHO. Are you sure you did not use CPAN or something like that to install perl modules that were not installed by default?

I suggest to invest in something like a UPS or filter the power line. It might save you some issues.
Title: Re: Corrupted Perl
Post by: besterl on May 04, 2011, 04:58:23 PM: I have a UPS installed, but the power failures are extended (couple of hours) and UPS eventually runs out

This happened about 5 or 6 nights in a row

There was other orruption as well, but fsck seem to sorted it

The big problem was mail not starting up due to the corrupted perl modules.

But all is fine now, and the guys are shutting down the server in the evenings if they cannot start the generator during power failures.
Title: Re: Corrupted Perl
Post by: Stefano on May 04, 2011, 05:00:02 PM: Quote from: besterl on May 04, 2011, 04:58:23 PM
I have a UPS installed, but the power failures are extended (couple of hours) and UPS eventually runs out

nut is your friend :-)
Title: Re: Corrupted Perl
Post by: janet on May 04, 2011, 06:26:08 PM: besterl

Quote
I have a UPS installed, but the power failures are extended (couple of hours) and UPS eventually runs out

You should configure NUT which will automatically shut down the server & UPS in an orderly fashion and then configure your UPS & server BIOS to restart when mains power returns.
Other UPS software running on the server can also do this.
Title: Re: Corrupted Perl
Post by: besterl on May 05, 2011, 05:49:31 PM: I have APC UPS with only a single USB port.

The client want that to shut down the Windows Server.

So - yes - in an ideal world I can use nut, but in the real world people see the Windows server as more important.

I think the next UPS must have a network management port and support few devices over IP.........

Thanks for all your feedback - it always gives new ideas.
Title: Re: Corrupted Perl
Post by: janet on May 06, 2011, 11:49:37 AM: besterl

You can set up Master & Slave servers so that more than one server (and even Windows workstations connected to the same "big" UPS) is/are shutdown in the event the UPS is about to shutdown.
I have done it myself in the past (I think using APCUPSD) but the info is not quickly accessible.
ie I had SME server interacting with the UPS via connected cable (software in Master mode), and then the Windows server & workstations were controlled via the LAN cable. You need to run software on each other server & workstation (software in Slave mode).

Search these forums back quite a few years as I think it has been covered here, or search Nut & APCUPSD on the net for further answers. Maybe someone else here can provide more details.