Topic: internal server errror

[sandoz]

after upgrading quite some packages on my SME server i cannot login anymore, getting the internal server error.

What could have gone wrong?

admin_error_log:
[Tue Jun 12 10:26:33 2007] [error] [client 127.0.0.1] Premature end of script headers: login
[Tue Jun 12 10:31:53 2007] [error] [client 127.0.0.1] [Apache::AuthTkt] open of config file '/etc/e-smith/web/common/cgi-bin/AuthTKT.cfg' failed: No such file or directory at /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/Apache/AuthTkt.pm line 74.
[Tue Jun 12 10:31:53 2007] [error] [client 127.0.0.1] Premature end of script headers: login
[Tue Jun 12 10:32:19 2007] [error] [client 127.0.0.1] [Apache::AuthTkt] open of config file '/etc/e-smith/web/common/cgi-bin/AuthTKT.cfg' failed: No such file or directory at /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/Apache/AuthTkt.pm line 74.
[Tue Jun 12 10:32:19 2007] [error] [client 127.0.0.1] Premature end of script headers: login

[bpivk]

What exactly did you update?

[tog]

Hmmmmm... I found your post because I got the same trouble:


[Thu Jun 14 09:23:41 2007] [error] [client 127.0.0.1] Premature end of script headers: login
[Thu Jun 14 09:23:44 2007] [error] [client 127.0.0.1] [Apache::AuthTkt] open of config file '/etc/e-smith/web/common/cgi-bin/AuthTKT.cfg' failed: No such file or directory at /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/Apache/AuthTkt.pm line 74.
[Thu Jun 14 09:23:44 2007] [error] [client 127.0.0.1] Premature end of script headers: login



I assume this is a bug.  I will go have a look see and perhaps open a bug.  If anyone figures it out, please post.

[tog]

You may have to run this command in a shell:

signal-event post-upgrade; signal-event reboot

It fixed it for me.  Seems that the last update put in place a new login system.  After I ran that command, I got a web page login instead of a browser prompt.

I think it'd be useful for the server to somehow indicate that we need to run "signal-event post-upgrade; signal-event reboot" after an update.  This has messed me up a couple times.  I wish the web admin page for the updates had the option to call "signal-event post-upgrade; signal-event reboot" after the update.

[raem]

tog

> I think it'd be useful for the server to somehow indicate that we need to > run "signal-event post-upgrade; signal-event reboot" after an update.  

It usually does do that if you are using the server manager panel to update your server, so if you are not seeing that behaviour please report it as a bug.


>  I wish the web admin page for the updates had the option to
> call "signal-event post-upgrade; signal-event reboot" after the update.

Again it usually proceeds to do that automatically after upgrades via the server manager panel. Look at the end of the page after updates appear to have finished. Please report as a bug if it is not doing so for you.

Alternatively the option is available under the Administration/Reboot or shutdown panel,
select the Reconfigure option, which then runs those commands.

[raem]

tog

> I think it'd be useful for the server to somehow indicate that we need to > run "signal-event post-upgrade; signal-event reboot" after an update.  

I just ran an update on a sme7.1.3 server and at both the top and bottom of the server manager screen, I got the message below (and I also had a Reconfigure button at the bottom of the page too).

"The system needs to be reconfigured after adding or removing software, or applying updates.

Please click on the Reconfigure button at the bottom of this page to start the reconfiguration process. An automatic reboot will be initiated as part of this reconfiguration process "

[tog]

You know what, I just ran an update and noticed that (after my post) my prayers have been answered.

Did you try this sandoz???