Error : eth0 error fetching interface information

[iamhatinh]

I install : CentOS 5
RAM : 256MB
Disk Space : 10 GB

when i install directadmin , have problem

Is eth0 your network adaptor with the license IP? (y,n) : y
eth0: error fetching interface information: Device not found
eth0: error fetching interface information: Device not found

Check my current IP by executing:

ifconfig eth0

Result:

eth0: error fetching interface information: Device not found

Pls help !
Thanks

 

[floyd]

Sounds like you may be on a VPS in which case your interface may not be eth0.

http://www.directadmin.com/installguide.html

Use ifconfig by itself to find your interface name.

 

[iamhatinh]

Sounds like you may be on a VPS in which case your interface may not be eth0.

http://www.directadmin.com/installguide.html

Use ifconfig by itself to find your interface name.

DirectAdmin Installation Guide

Special notice for VPS/VDS installs:
After the install, add:

ethernet_dev=eth0:devicename

to /usr/local/directadmin/conf/directadmin.conf.

Replace devicename with the FULL devicename reported by ifconfig. If your VDS/VPS system emulates eth0, then you may skip this step.

I have added :
ethernet_dev=eth0:mydomain (then try IP VPS )

Restart VPS and

[root@xxx ~]# ifconfig eth0
eth0: error fetching interface information: Device not found

ifconfig

Result:

[root@xxxx ~]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.
255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:488 errors:0 dropped:0 overruns:0 frame:0
TX packets:445 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:54851 (53.5 KiB) TX bytes:67650 (66.0 KiB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
inet addr:66.xxx.x.xx P-t-P:66.xxx.x.xx
Bcast:67.xxx.x.xx
Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
inet addr:66.xxx.x.xx P-t-P:66.xxx.x.xx
Bcast:66.xxx.x.xx
Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

How can i find "devicename" ?
Is that hostname ?

 

[floyd]

Which one of the interface's matches the ip your directadmin license is on?

 

[rmwebs]

I think its the first (venet0:0)

Although I've tried that on my VPS and it doesnt work.

Tried: ethernet_dev=eth0:venet0:0

 

[floyd]

I hope you meant

ethernet_dev=venet0:0

 

[proHSP]

Looks like there is a error in the installation guide - eth0: is not needed, only venet0:0

 

[floyd]

Its assumed you know venet0 would replace eth0. They cannot just arbitrarily say ethernet_dev=venet0:0 because not all VPS's will use venet. Some VPS's will still use eth0. Its up to the admin to know the difference. If you didn't know it before then you know it now. DirectAdmin is not for first time administrators.

 

[Dravu]

Its assumed you know venet0 would replace eth0. They cannot just arbitrarily say ethernet_dev=venet0:0 because not all VPS's will use venet. Some VPS's will still use eth0. Its up to the admin to know the difference. If you didn't know it before then you know it now. DirectAdmin is not for first time administrators.

It says in the instructions to just replace "devicename", not also "eth0:". If eth0 needs replacing with it, then they should say to replace "eth0:devicename" and not just "devicename".

Yes, it probably is somewhat common sense. But it's still needed since it CAN cause some confusion among users.

 

[DirectAdmin Support]

Hello,

I've updated the installguide.html with more clear information.
Thanks for pointing it out

John