Separate names with a comma.
Discussion in 'General Discussion' started by nybble, Oct 31, 2004.
Since last week..
zcat: ./cancel.1.gz: No such file or directory
Yep, getting it here. Sounds like it's RHE.
I really don't get it.
All these big hosts - like 1and1, all have their own control panel that never has any bugs. Never flops out, and is always there for users to use without problem.
On top of that there is thousands of servers at some of these places and none of them require 60 hours of babysitting a month to look after.
I don't get it... why can't cpanel just be stable?
Yep I get this too when running the makewhatis cron script I am running 9.9.8-E52 on RHEL3
Makewhatis has nothing to do with cPanel.
Makewhatis is a unix program that builds the man pages and the whatis database.
For that error, check to see if this exists /usr/share/man/man1/cancel.1.gz
No that file is not there, that was my first thought.
How do you know they don't have bugs? You have access to their servers? You admin a 1&1 server lately?
Have you ever used plesk? ensim? directadmin? Are they perfect? If so, you might give them a shot.
In all seriousness, cPanel has more features than any other control panel, more features tends to mean more bugs. However, the above that you are whining about, has NOTHING to do with cPanel.
With that said, I do notice bugs occasionally, but I report them, and they get resolved.
Everything has its bugs I am just saying it seems large hosting providers tend to have fewer bugs than the panels out there right now :|
Anyway, I was just going on to fill up some space. I'm happy with cpanel it just seems to have new bugs every few days
So any solution to this?
Same problem here:
Since so many of us are getting this, I'm going to assume it's a bug but does anyone have a fix?
rm -f /usr/share/man/man1/cancel.1.gz
Umm, that file doesn't exist in the first place... so deleting it again isn't going to do anything.
The error comes about because that file (or one in a similar place do a search for cancel.1.gz) is a symlink to a non-existent file. Get rid of the link, get rid of the problem.
See if you can follow this logic.
/usr/share/man/man1]# ls -l cance*
lrwxrwxrwx 1 root root 33 Sep 22 05:41 cancel.1.gz -> /etc/alternatives/print-cancelman
/etc/alternatives]# ls -l print-cancelman
lrwxrwxrwx 1 root root 36 Sep 22 05:41 print-cancelman -> /usr/share/man/man1/cancel-cups.1.gz
/usr/share/man/man1]# ls -l cancel-cups*
lrwxrwxrwx 1 root root 7 Sep 22 05:41 cancel-cups.1.gz -> lp.1.gz
/usr/share/man/man1]# ls -l lp.1*
lrwxrwxrwx 1 root root 29 Sep 22 05:41 lp.1.gz -> /etc/alternatives/print-lpman
/etc/alternatives]# ls -l print-lpman
lrwxrwxrwx 1 root root 32 Sep 22 05:41 print-lpman -> /usr/share/man/man1/lp-cups.1.gz
And it keeps going, the trick is to find the missing link in the never ending chain.
I've done this and I'll find out next week if it worked!