Arch Linux

Angle

Member

Registered: 2009-06-15

Posts: 21

System Update & Catalyst Problems :/

Alright, so usually upgrades are painless, I just have to remember to reinstall catalyst-utils and my wireless driver and everything goes smoothly. Apparently not this time.
After doing a full system upgrade, I did my usual regimen  and I even ran aticonfig again, just incase. But this time all I can get is this error message.

hostname: Host name lookup failure
xauth:  creating new authority file /home/angle/.serverauth.4043


This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.6.3.901 (1.6.4 RC 1)
Release Date: 2009-8-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH x86_64 
Current Operating System: Linux arch 2.6.31-ARCH #1 SMP PREEMPT Fri Oct 23 10:03:24 CEST 2009 x86_64
Build Date: 04 September 2009  05:45:43PM
 
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 28 16:05:15 2009
(==) Using config file: "/etc/X11/xorg.conf"
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found

waiting for X server to shut down

I don't know what else info you may need to help troubleshoot this but if you need anything else, just ask. Thanks.

Last edited by Angle (2009-10-29 11:15:59)

ngky

Member

Registered: 2009-10-29

Posts: 5

Re: System Update & Catalyst Problems :/

Hi Angle!
I encountered the same problem as you after doing an upgrade, about 3-4 days ago.
I do not have catalyst-utils installed

When I 'startx' with my non-root account, I see "hostname: Host name lookup failure" too.
I hadn't been able to find out what exactly is wrong.

I did the following as abc:

abc@mymachine :~$ hostname -v
gethostname()=`mymachine'
mymachine

abc@mymachine :~$ hostname -vf
gethostname()=`mymachine'
Resolving `mymachine' ...
hostname: Unknown host

abc@mymachine :~$ hostname -va
gethostname()=`mymachine'
Resolving `mymachine' ...
hostname: Unknown host

Now the following is strange because this should never happen ...

abc@mymachine :~$ strace hostname -f
...
open("/etc/hosts", O_RDONLY|O_CLOEXEC)  = -1 EACCES (Permission denied)
...

There is no problem if I run the following commands root user.

root@mymachine :~# hostname -v
gethostname()=`mymachine'
mymachine

root@mymachine :~# hostname -vf
gethostname()=`mymachine'
Resolving `mymachine' ...
Result: h_name=`mymachine.localdomain'
Result: h_aliases=`localhost.localdomain'
Result: h_aliases=`localhost'
Result: h_aliases=`mymachine'
Result: h_addr_list=`127.0.0.1'
mymachine.localdomain

root@mymachine :~# hostname -va
gethostname()=`mymachine'
Resolving `mymachine' ...
Result: h_name=`mymachine.localdomain'
Result: h_aliases=`localhost.localdomain'
Result: h_aliases=`localhost'
Result: h_aliases=`mymachine'
Result: h_addr_list=`127.0.0.1'
localhost.localdomain localhost mymachine

So I am quite optimistic my /etc/hosts and /etc/rc.conf files are okay.

Last edited by ngky (2009-10-29 11:39:17)

Angle

Member

Registered: 2009-06-15

Posts: 21

Re: System Update & Catalyst Problems :/

Well the hostname is the least of my worries right now, I just want X to work D:

ngky

Member

Registered: 2009-10-29

Posts: 5

Re: System Update & Catalyst Problems :/

What do your /etc/rc.conf and /etc/hosts files look like?
Somehow I feel that you cannot run X because of the hostname problem.
Did you recently change your machine's HOSTNAME?

Mine looks like this
/etc/rc.conf

HOSTNAME="mymachine"

and in /etc/hosts

127.0.0.1       mymachine.localdomain localhost.localdomain localhost mymachine

Despite seeing the hostname error, I can run X this time.
But I have problems using the Juniper Networds webvpn service.
When I start the webvpn, I am assigned an IP address as usual.

As root, I checked these files [note: I had changed the IP addresses and hostnames for display purposes]
# cat /etc/resolv.conf
search dns.private.network
nameserver 125.110.0.254
nameserver 125.110.0.252
nameserver 161.19.100.88
nameserver 161.19.83.88

# cat /etc/hosts
# BEGIN hosts added by Network Connect
125.110.10.80   webvpn.private.network
# END hosts added by Network Connect
127.0.0.1       mymachine.localdomain localhost.localdomain localhost mymachine

Then when I try to ssh to a server in a private network as a non-root user,
I get the following problem

ssh: Could not resolve hostname machine.private.network:
Temporary failure in name resolution

On the other hand, if I ssh to machine.private.network as root, I am prompted for the password and I can log in to the private machine.

Are there others with similar problems after the recent upgrade?

Angle

Member

Registered: 2009-06-15

Posts: 21

Re: System Update & Catalyst Problems :/

Alright thanks ngky, I fixed the hostname. I must have forgotten to change the /etc/hosts file when I reinstalled Arch. The hostname is fixed now but I still get that fglrx error....

ngky

Member

Registered: 2009-10-29

Posts: 5

Re: System Update & Catalyst Problems :/

glad that you fixed your hostname.
can't help with your fglrx though...

orjanp

Member

From: Tromsoe, Norway

Registered: 2004-07-03

Posts: 347

Re: System Update & Catalyst Problems :/

It seems to be something wrong with your xorg.conf file.

We need to see it.

---

Ørjan Pettersen

ngky

Member

Registered: 2009-10-29

Posts: 5

Re: System Update & Catalyst Problems :/

I've solved my problem so I guess it's good to post it here.

What caused the problem:
Because I wanted to have all my files to have the permission -rw------ by default,
I changed umask 022 to umask 077 in either .profile or .bashrc (cannot recall because I reformatted my computer).
Then I ran Juniper Network's webvpn.
The webvpn program changed the contents in /etc/hosts and /etc/resolv.conf
Both /etc/hosts and /etc/resolv.conf are supposed to be -rw-r--r--
But due to the umask being changed to 077, the permission bits become -rw------
Thus, my normal-user account encountered the hostname lookup problem.

So I changed the umask back to 022 and everything works again.