Topic: Update to 7.3 - yum fatal errors

[eastend99]

Hello,

today I updated an SME server from 7.2 to 7.3. Yum reported FATAL errors.
The system reports to be 7.3 in server manager and seems to be working fine. The only error I found so far is webmail: it generates a 404 NOT FOUND error message

Code: [Select]

The requested URL /webmail//imp/redirect.php was not found on this server(note the double backslash).

This is the part of the yum.log with the errors:

Code: [Select]

  Updating  : kmod-ppp                     ####################### [18/86]
FATAL: Could not open '/boot/System.map-2.6.9-67.0.1.EL': No such file or directory
  Updating  : e-smith-samba                ####################### [19/86]
  Updating  : dmraid                       ####################### [20/86]
  Updating  : kmod-slip-smp                ####################### [21/86]
FATAL: Could not open '/boot/System.map-2.6.9-67.0.1.ELsmp': No such file or directory
  Updating  : kmod-appletalk-smp           ####################### [22/86]
FATAL: Could not open '/boot/System.map-2.6.9-67.0.1.ELsmp': No such file or directory
  Updating  : rkhunter                     ####################### [23/86]
  Updating  : kmod-slip                    ####################### [24/86]
FATAL: Could not open '/boot/System.map-2.6.9-67.0.1.EL': No such file or directory
  Updating  : zip                          ####################### [25/86]
  Updating  : kmod-appletalk               ####################### [26/86]
FATAL: Could not open '/boot/System.map-2.6.9-67.0.1.EL': No such file or directory
  Updating  : libacl                       ####################### [27/86]
  Updating  : smeserver-release            ####################### [28/86]
  Updating  : e-smith-openssh              ####################### [29/86]
  Updating  : kmod-ppp-smp                 ####################### [30/86]
FATAL: Could not open '/boot/System.map-2.6.9-67.0.1.ELsmp': No such file or directory
  Updating  : e-smith-nutUPS               ####################### [31/86]
Can someone explain what went wrong? And hopefully tell me what to do to get it right?

Regards,

Marcel

[jester]

Marcel,

Your better off opening a bug for your problem in the bug-tracker!

[CharlieBrady]

Marcel,

Your better off opening a bug for your problem in the bug-tracker!

Marcel should open two bugs, one for each issue he has discovered.

[cactus]

Marcel,

Your better off opening a bug for your problem in the bug-tracker!

Both errors are probably already in the bugtracker, but I know for sure the latter (about the not found files on the /boot) are deemed irrelevant and would not be of any harm: http://bugs.contribs.org/show_bug.cgi?id=3696

Perhaps this bug might help you with the webmail problem: http://bugs.contribs.org/show_bug.cgi?id=3707

[eastend99]

After some investigations I found out that:

The errors in the yum log are exactly the same as the bug metioned by Cactus.
I did enter the error message 'FATAL: Could not open' into the bugzilla search window.
I would have expected bug 3696 to show up there since the search string is in the bug description in clear text.
Bugzilla keeps calling Zarro boogs found..... I tried some other applicable search strings but 3696 does not show up.
How can I find this bug trough the search facility?

The broken webmail problem was resloved after a signal-event post-upgrade and a signal-event reboot.
This case differs from bug 3707 because I do not have any additional horde modules installed.
If you think it is necessary to open a new bug anyway, I will do so.

Thanks for your advice!

Regards,

Marcel

[cactus]

After some investigations I found out that:

The errors in the yum log are exactly the same as the bug metioned by Cactus.
I did enter the error message 'FATAL: Could not open' into the bugzilla search window.
I would have expected bug 3696 to show up there since the search string is in the bug description in clear text.
Bugzilla keeps calling Zarro boogs found..... I tried some other applicable search strings but 3696 does not show up.
How can I find this bug trough the search facility?

To search in the comments you need to have the advanced search option, the normal search searches only in summary and by bug number AFAIK.

The broken webmail problem was resloved after a signal-event post-upgrade and a signal-event reboot.
This case differs from bug 3707 because I do not have any additional horde modules installed.
If you think it is necessary to open a new bug anyway, I will do so.

Unless you did a signal-event reconfigure; signal-event reboot (or a reconfigure in the server-manager) after the update you should report it as a bug, if you did not do so, you just left out part of the update procedure and it would be a user error and not a bug.

[eastend99]

Just to be sure:

Unless you did a signal-event reconfigure; signal-event reboot (or a reconfigure in the server-manager) after the update you should report it as a bug, if you did not do so, you just left out part of the update procedure and it would be a user error and not a bug.

I did a manual yum update on the command line logged in as root.
I checked the command line history. I did:

Code: [Select]

yum update
signal-event post-upgrade; signal-event reboot This is what yum reports to do next after an update (to be exact: I copied yum output and pasted it back to the command line)

This is what I get when I enter signal-event reconfigure on the commandline:

Code: [Select]

signal-event reconfigure
Can't open directory /etc/e-smith/events/reconfigure

I am sure I had to do the signal-event post-upgrade; signal-event reboot command twice to get webmail running again.

[cactus]

This is what I get when I enter signal-event reconfigure on the commandline:

Code: [Select]

signal-event reconfigure
Can't open directory /etc/e-smith/events/reconfigure

I am sure I had to do the signal-event post-upgrade; signal-event reboot command twice to get webmail running again.

Reconfigure is the name of the option in the server-manager, it won't work on the command line. The reconfigure in server-manager merely executes the same two statements that you can manually start from the command line for you without bothering about the command line.