Mailperm shadow is a link. Not changing ownership. Error with 9.9.3 Upgrade

[lloyd_tennison]

Mailperm Error "shadow is a link. Not changing ownership." Error with 9.9.3 Upgrade

With the 9.9.3 update today, running mailperm now gives the following errors for every domain:

/home/mecom/etc/me.com/shadow is a link. Not changing ownership.
/home/mecom/etc/me.com/passwd is a link. Not changing ownership.

Something does not sound right - especially when they are most definitely NOT links.



[email protected] [/home/mecom/etc/me.com]# ls -lh
total 8.0K
drwxr-x--- 2 mecom mail 4.0K Oct 3 23:00 ./
drwxr-x--- 3 mecom mail 4.0K Oct 3 23:00 ../
-rw-r--r-- 2 mecom mail 0 Oct 3 23:00 passwd
-rw-r--r-- 2 mecom mecom 0 Oct 3 14:18 quota
-rw-r----- 2 mecom mail 0 Oct 3 14:18 shadow
[email protected] [/home/mecom/etc/me.com]#

I do not know if there are any errors - but it is not good that an error checker has an error.

(Mailperm was last run about three hours before.)

 

[nickn]

run /scripts/updatenow &/or upcp manual again. You should be on 9.9.4-CURRENT_4 now.

 

[lloyd_tennison]

Hmm, changelog says it ran, but WHM says 9.9.3. WIll try and see what happens.

Ran it - but in the history it states:


total size is 1634184 speedup is 199.05
Fetching http://httpupdate.cpanel.net/cpanelsync/RELEASE/cpanel/version....100%......Done
Versions Match! (9.9.3-RELEASE_17). You are running the latest RELEASE.


Is there a problem with the location upcp is getting the update from - like not updated at Cpanel????

 

[MarlboroMan]

9.9.4 is only out on the EDGE/CURRENT trees - check out http://forums.cpanel.net/showthread.php?t=30800&page=4 - Nick stated RELEASE/STABLE trees should be updated tomorrow.

FYI, the way cPanel's mailsystem works is HARD links, not symbolic. So they're still links, but they don't look like them.

 

[Chris2k3]

This problem still exists in 9.9.4-CURRENT_3

 

[deddy]

/scripts2/mailperm

I'm still on WHM 9.9.0 and cPanel 9.9.2-R7 and got the same error.
Strange but it looks like it has something to do with the new Apache,
mod_ssl/2.8.20 upgrade.

That is unbelievable :

After Apache/mod_ssl 2.8.20 upgrade the same problem
on WHM 9.4.0 and cPanel 9.4.1-S65

shadow is a link. Not changing ownership.
passwd is a link. Not changing ownership.

to all user accounts.

/scripts/updatenow is also involved in the Apache upgrade
script and is the real source of that problem, because it is
updating the "mailperm" script.

We have to wait until this script has been fixed.

 

[krisdv]

I'm still running 9.9.2 S8 with mod_ssl 2.8.19 and have the same problem. Someone opened a support ticket for this?

 

[nickn]

They are aware of this and working on it. Will only require a /scripts/updatenow

 

[deddy]

/scripts/updatenow

isn't able to get rid of that problem

 

[nickn]

It's not fixed yet.

 

[jester.ro]

i get the same thing, and it's not related to any apache/modssl updates.

i still have mod_ssl .18, and i am on 9.9.3-R17, so i only updated cpanel, and got these mailperm errors.


and please, stop saying updatenow fixes this.
it may fix it if you're on edge, but most of us are running stable/release only, so this is not a fix for us.

anyway, doesn't seem like a big error there...except i have mailperm running in cron avery 5 minutes(lots of inbox.lock problems), and i get lots of mail. I think i'll make the cron without output

 

[dgbaker]

The error has to do with the /scripts/saftebits.pl perl script. The way it checks for the files for some reason when it comes across the period in the domain name it disregards it and classifies it as a symlink instead. This seems to be more of syntax issue, but I'll leave that to Nick et al to say what is/was wrong.

This one in fact, if you run the updatenow with the last 12 hours or so, will cause the issue as it will update to the new files to fix other security issues.

 

[Chris2k3]

seems to be fixed

 

[deddy]

Yes it is :D

 

[screege]

How did you fix it? I only run stable versions.

Thank you

 

[deddy]

/scripts/updatenow

 

[lloyd_tennison]

I am running on Release and the update fixed it. Sorry, I am not that conservative to run on Stable - but I did not think the problem was there. So if nothing else - you can upgrade to release. Otherwise, maybe someone else can help.