Network (NIC) Not Running

[partho]

I have Installed GoAutoDial "goautodial-32bit-ce-3.0-RC1a.iso" on IBM Xeon Server (even tried other Two More PC) and after Installed Every Time showing Network(NIC) not running.
Each Machine has
1. 2 NIC (Driver auto installed by goautodial)
2. I can Ping internal network & external network after setting local & live IP.
3. 'yum updated' done
4. nano /etc/sysconfig/network-scripts/ifcfg-eth0 & eth1
DEVICE=eth0
BOOTPROTO=static
HWADDR=5a:f3:a3:2f:f2:5b
ONBOOT=yes
NETMASK=255.255.255.248
IPADDR=x.x.x.x
GATEWAY=x.x.x.x
TYPE=Ethernet

DEVICE=eth1
HWADDR=5a:13:1c:1c:f2:5a
ONBOOT=yes
HOTPLUG=
BOOTPROTO=static
TYPE=Ethernet
NETMASK=255.255.255.0
IPADDR=192.168.1.3

5. Updated server ip by /usr/share/astguiclient/ADMIN_update_server_ip.pl
6. Server Restarted but nothing happened.

Please Help needed.
by the way on those PC GoAutodial 2.1 was working fine & Running

[williamconley]

What do you mean by: "Every Time showing Network(NIC) not running"?

Is this a message you see somewhere or ...?

Doesn't Goautodial have a network management utility in one of the goautodial web pages on the server?

Doesn't the Goautodial Wiki (on the goautodial site from which you downloaded goautodial) have instructions for altering the IP?

When you say "server restarted but nothing happenend", you lost me entirely. If you restarted the server ... the "thing" that happened was that the server restarted. Are you saying that the NIC reset and did not have the IP after reboot?

I believe CentOS has a net-config utility that you should be using for this (which may be overwriting your settings?). But since I'm not entirely sure what your problem is to begin with ... I don't want to delve any further until that is clear.

Have you considered installing with Vicibox.com's iso instead of Goautodial? (If there is a driver issue or an install issue ... the other installer may make you happier ... )

[partho]

See this picture
goo.gl/R7BPjm
goo.gl/aQz8Yv

I have Installed on IBM Xeon 'System 3250 M3' Server and The installaion was just fine, without any problems, and the NICs is recognized by the OS, and is up( ifconfig), and I configure both of them, One is for Internal Network and another one for LIVE IP which is use for DID and both them working fine as i checked with Ping Command (i can Ping google as well internal network) but when ever i type 192.168.1.3(gotoautodial server), it is not running - showing.

In Vicidial 2.1 Server it is working (installed back this version) & working fine and network is functioning. Dialing also done though that.
So I thought I made mistake, now this time I update with 'yum update' same server from 2.1 to 3.0 as instructed in web site and every step is smoothly done. After Restart it showing same thing! I was shocked and tried all possibilities and left that version 3 and goes back to 2.1.

[williamconley]

! LOL.

So you see a "not running" notification on the goautodial status panel, but everything works.

We've never bothered with the cute status screen in Goautodial. And just so you know, there is no "Vicidial 2.1" it's Goautodial 2.1 which is an Installer for Vicidial. Your vicidial version is more likely 2.4. The version that is listed with a Build number after it is the Vicidial version. Vicidial is the Dialer software that you're actually using. Underneath some slightly modified web pages, Vicidial's scripts are controlling Asterisk.

So: Asterisk is the PBX (the telephone server). Vicidial controls Asterisk to make it a Predictive Autodialer. Goautodial is ... just the installer. Another installer named Vicibox will do the same thing, but without the Goautodial logos or pretty screens. If you like the pretty status screens, there is a very cool application called Webmin that has a lot more power than Goautodial. But goautodial also has some nice wizards (to help beginners get going) and is very easy to install.

I would not be worried if everything worked but the NIC status showed "Not running". After all, if everything works obviously the NIC is working and the goautodial status screen is wrong.

That being said, since we have never had a client request that we look into that status page, we have no experience with it. Happy to help, if you post the source code responsible for the error we may be able to help you troubleshoot it.

It could be that your hardware or NIC is either too old or too new for the drivers to work properly. Or perhaps they are reporting information in an odd fashion and goautodial cannot parse the data properly.

[gardo]

Looks like the data is not getting parsed properly by the "System Services" widget. If you're not having problems then this is really safe to ignore. Is your GOautodial CE 3.0 server working properly aside from "NIC not running" message?