Topic: Just applied latest updates - cannot get into admin panels

[judgej]

I've just applied a bunch of yum updates that came through this morning, and now I cannot get into the admin panels. The server tells me that my browser does not support cookies, but I know it does.

Also there are some problems sending e-mail, with clients being refused connections to the SMTP server. That may be options that have been reset in the admin panel, but until I can get into it, I can't check.

Any clues what may have gone wrong?

-- Jason

[judgej]

Aha - the admin panal now requires me to use the full domain 'sme.mydamain.co.uk/server-manager' rather than just the server name 'sme/server-manager'.

SMTP works for some machines, but not others, so I suspect the problem may be the same: they are using just the server name rather than the fully-qualified domain and name.

Update: it seems to be OSX Mail that no longer wants to sent mail through the SME server. We have checked its settings, deleted and reconfigured the SMTP settings, tried both SSL and non-SSL, but it just refuses to send mail. Thunderbird from the same Mac works fine.

-- JJ

[stephen noble]

http://bugs.contribs.org/show_bug.cgi?id=2402

[judgej]

http://bugs.contribs.org/show_bug.cgi?id=2402

Thanks. I've added a note to explain why I think the cookies are not being accepted by the browsers. I believe there may be a '.' prefix missing from the cookie domain.

I think also that the update is preventing OSX Mail from sending mail, but I need to do some more analysis before I can raise a bug.

-- JJ

[CharlieBrady]

I think also that the update is preventing OSX Mail from sending mail, but I need to do some more analysis before I can raise a bug.

Please raise the bug and then do the analysis, attaching the results to the bug. Thanks.

[idyll]

I immediately tested sending with OS-X and found no issue.

FYI.

patrick

[jimgoode]

I installed 6.0.1-01 and upgraded to 7.1 this morning. All access and functioning appeared to work normally.

I used the server-manager panel to apply a lot of updates via yum. After reboot, the system will not come all the way up. I am stuck with:

Booting 'SME Server (2.6.9-42.0.10.ELsmp)'

root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.9-42.0.10.ELsmp ro root=label=/
   [Linux=bzImage, setup=0x1400, size=0x15db7b]
initrd /initrd-2.6.9-42.0.10.ELsmp.img
   [Linux-initrd @ 0x7f90000, 0x5f21e

Uncompressing Linux... Ok, booting the kernel.

I tried the rescue mode and entered 'chroot /mnt/sysimage' but get exactly the same result. Any ideas what I'm running up against?

Thanks,
Jim

[bpivk]

Did you try any other kernels? Some older ones.

[jimgoode]

I have several kernels to choose from. The result of each are as follows:
vmlinuz-2.6.9-42.0.3.EL          OK
vmlinuz-2.6.9-42.0.3.ELsmp    OK
vmlinuz-2.6.9-42.0.8.ELsmp    hangs
vmlinuz-2.6.9-42.0.10.EL        OK
vmlinuz-2.6.9-42.0.10.ELsmp   hangs

In the process of going in and looking at the files in the /boot directory I see that 3 files are bogus links. module-info, System.map and vmlinuz all point to non-existent files. Example: vmlinuz -> vmlinuz-2.4.20-18.7
Is that the problem?

[judgej]

I immediately tested sending with OS-X and found no issue.

Was that sending via port 25, or SSL? I think our port 25 works, but SSL and OSX doesn't. It is a shame that OSX does not give us any more detail other than "cannot send message, would you like to try a different SMTP server?".

We have a few other Macs we can try, so will continue to look at this issue (whether it is just us or something wider). What I'm not sure about, is which log file I need to inspect on the server. There ought to be a log file that lists the SMTP connection attempts and results, but I can't seem to see it.

-- JJ

[bpivk]

You should post this to the bugtracker because i think that it's a kernel problem.

[idyll]

We use secure mail, so it was using port 465. No issue on two machines, each on the latest version of OS-X.

I made no  client changes and used yum to perform the update.

I think it caches the SSL part, have you tried removing the SSL option, then re-enabling it?

regards,

patrick

[judgej]

We use secure mail, so it was using port 465. No issue on two machines, each on the latest version of OS-X.

I made no  client changes and used yum to perform the update.

I think it caches the SSL part, have you tried removing the SSL option, then re-enabling it?

Thanks. That's all good to know.

We did try removing certificates and various options from the Mac, but we haven't tried disabling and enabling it again on the server. That's worth a try.

-- JJ

[judgej]

I see there is a fix for this issue now, but it didn't quite make it into 7.1.2. I look forward to trying it out at the next set of updates. Thanks for all the hard work!

-- JJ