Network centre problem? [SOLVED]

[muungwana]

to any person with the problem,
open the terminal,log in as root,run "draknetcenter",try to disconnect/connect and report any output on the teminal

[oldgreygary]

I ran the draknetcenter from the terminal and the following message was displayed on the console.

Failed to kill daemon. (No such file or directory)


It connects ok and the icon changes from a red cross to a green tick. But trying to disconnect repeats the message and the icon stays as a green tick. So, I think it does do the disconnect but it is the icon that does not change. Someone has mentioned that earlier I think?



If there is anymore information you need let me know.

Cheers for now

[uggy]

I don' know if this helps

Code: [Select]

[root@localhost uggy]# draknetcenter
comgt 18:42:26 -> -- Error Report --
comgt 18:42:26 -> ---->                      ^
comgt 18:42:26 -> Error @116, line 7, Could not write to COM device. (1)

comgt 18:42:31 -> -- Error Report --
comgt 18:42:31 -> ---->                       ^
comgt 18:42:31 -> Error @74, line 4, Could not write to COM device. (1)

Note: Whilst connected, right click NetApplet > disconnect, does disconnect but still displays green tick (connected)
        Whilst connected, opening draknetcenter, displays connected, press disconnect, it does disconnect but still displays as connected and offers a disconnect button, which will now not work a second time.

[muungwana]

I ran the draknetcenter from the terminal and the following message was displayed on the console.

Failed to kill daemon. (No such file or directory)


It connects ok and the icon changes from a red cross to a green tick. But trying to disconnect repeats the message and the icon stays as a green tick. So, I think it does do the disconnect but it is the icon that does not change. Someone has mentioned that earlier I think?

If there is anymore information you need let me know.

Cheers for now

That could be the cause of the problem you have,hope those who knows the ins and outs of the netcenter will have an idea of what is broken.

why are you connecting and disconnecting wired interface? most people only do that with wireless interface

[oldgreygary]

That could be the cause of the problem you have,hope those who knows the ins and outs of the netcenter will have an idea of what is broken.

why are you connecting and disconnecting wired interface? most people only do that with wireless interface

Old habits die hard, I only used to have a dial-up wired connection so had got into a routine of disconnecting/reconnecting.....

Gary

[bicol_willem]

to any person with the problem,
open the terminal,log in as root,run "draknetcenter",try to disconnect/connect and report any output on the teminal

Well this might indicate something:

[willem@Home-PC ~]$ su
Password:
[root@Home-PC ~]# draknetcenter
(disconnecting leads to):
Failed to kill daemon. (No such file or directory)

Some deamon on the run?

The button "disconnect" remains active even after disconnecting.

I found the machine after this diconnected but Netapplet stubbornly says: Connected, but it doesn't show the usual wifi signal strength icon but the circle with checkmark instead.
Reconnect is no option other then through PCC.> Network & Internet (set up a new connection) or .. after a reboot.
Strange stuff!

[johnmart]

I have experienced pretty much all the same issues with network center.
One sure I found is that the network center appears to not respond, but if you click the refresh button, the display is refreshed & all is well. ymmv.

[OldGuy]

On my box NetApplet no longer shows disconnected, even if disconnected.

Can't remember when this started happening, but not a problem for me.

Has green tick displayed even after unplugging B/B dongle.

Same here +1, I know it's off by just bringing up Firefox and seeing it cannot connect to PCLinuxOS main.

It stays green check mark, not the usual red (off) signal.

[bicol_willem]

On my box NetApplet no longer shows disconnected, even if disconnected.

Can't remember when this started happening, but not a problem for me.

Has green tick displayed even after unplugging B/B dongle.

Same here +1, I know it's off by just bringing up Firefox and seeing it cannot connect to PCLinuxOS main.

It stays green check mark, not the usual red (off) signal.

Roger that. Unexpected we are on "something" here!    (Thought it was my install somehow).
Time for the "Big Gun's" to be deployed 

[joechimp]

Well, it is obvious by now that this a wider spread problem than each of us individually thought.

This is a more recent problem for me. As I never had this problem in the past.

[bicol_willem]

Well, it is obvious by now that this a wider spread problem than each of us individually thought.

This is a more recent problem for me. As I never had this problem in the past.

Same same same ... A recent problem.

Right now I see this:



I am connected wireless but don't see the signal indicator. (Isn't the case after a fresh reboot).
After a try to disconnect this icon pops up and seems to stay there till shutdown.

[oldgreygary]

I don't know if this is relevant  but these packages have been updated on my system in April:

Commit Log for Fri Apr  6 10:18:46 2012


Upgraded the following packages:
curl (7.23.1-1pclos2011) to 7.25.0-1pclos2012
drakx-net (0.87-6pclos2011) to 0.87-11pclos2012
drakx-net-text (0.87-6pclos2011) to 0.87-11pclos2012
libSDL1.2_0 (1.2.14-1pclos2010) to 1.2.14-3pclos2012
libcurl4 (7.23.1-1pclos2011) to 7.25.0-1pclos2012
libdrakx-net (0.87-6pclos2011) to 0.87-11pclos2012
libpurple0 (2.10.1-1pclos2011) to 2.10.3-1pclos2012
lomanager (3.5.1-2pclos2012) to 3.5.2-2pclos2012
luckybackup (0.4.6-1pclos2011) to 0.4.7-1pclos2012
opera (11.61-1pclos2012) to 11.62-1pclos2012
perl-Image-ExifTool (8.81-1pclos2012) to 8.85-1pclos2012
pidgin (2.10.1-1pclos2011) to 2.10.3-1pclos2012
plymouth (0.8.3-2pclos2011) to 0.8.3-5pclos2012


Commit Log for Tue Apr 10 19:29:26 2012


Upgraded the following packages:
dupeclean (1.2-1pclos2011) to 1.2-2pclos2012
dupeclean-gui (0.1-6pclos2011) to 0.1-7pclos2012
libsndfile1 (1.0.24-1pclos2011) to 1.0.25-1pclos2012
lomanager (3.5.2-2pclos2012) to 3.5.2-4pclos2012

Cheers for now

Gary

[kjpetrie]

I'm running one of the testing kernels (3.2.13-pclos5) and have the same problem.

The network center can control my eth0 connection, but doesn't read the result until it is closed and restarted. This applies to both connecting and disconnecting.

Clearly it isn't recognising the daemon's response or the response of the script which controls the daemon.

[uggy]

Not sure if this adds to the mix.



Screenshot of gkrell net monitor.  Something changed between 10 March/17 March.

Still monitors net traffic, but no connection times.

[AS]

Screenshot of gkrell net monitor.  Something changed between 10 March/17 March.

Still monitors net traffic, but no connection times.

there has been an update of drakx-net package and the underlying libs ... which is the package responsible for detecting the connectivity ...

which kernel are you running ?