Re: MM 0.6 conflicts with USB GPS device?
Quoting Dan Williams d...@redhat.com: Yeah, full debug output would be good then, since if MM sees that the device is not actually a modem, after probing it completely, it should never touch the device again unless the device goes away and re-appears. Here comes the normal and the debug log. You are right, that modem-manager does stop probing after some time, but this is after 55s, not 10s. The process does not respawn (PID stays the same), but does the AT+GCAP probe nine times with a distance between four and ten seconds. If there is a way to cut down the 55s more in the direction of 10s or 20s, this would be very helpful. mm.log.gz Description: GNU Zip compressed data mm-debug.log.bz2 Description: application/bzip ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
unknown reason error message in VPN connections
Hi NM !
I'm using the Network Manager on RHEL, and have just found that VPN stopped
working with no meaningfull log messages.
I've posted the details here in case anyone wants points :) :) :)
http://superuser.com/questions/602490/network-connection-failed-unknown-reason
And also reposted them below so that a record of this thread will be on the
NM archives (im sure it might be useful to somebody, someday)...
down vote
favoritehttp://superuser.com/questions/602490/network-connection-failed-unknown-reason#
Im on RHEL, and found that my VPN stopped working.
I discovered that I could use the command line utility, nmcli, to try to
get more info about what was happening.
However, Im finding that the vpn still seems to fail and the error has no
clear meaning:
[jvyas@jvyas jvyas]# nmcli con up id X
Active connection state: unknown
Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/11
state: VPN connecting (need authentication) (2)
state: VPN connecting (3)
state: VPN connecting (getting IP configuration) (4)suggested tags:
vpnnetworkingwireless-networking
Error: Connection activation failed: unknown reason.
So , to try some googling - I found the switch statement that this error
message is being returned from, and it looks like most conditions are
handled pretty well, which means something very funny must be going wrong
when i try to connect to VPN:
+static const char *
+vpn_connection_state_reason_to_string (NMVPNConnectionStateReason reason)
+{
+ switch (reason) {
+ case NM_VPN_CONNECTION_STATE_REASON_UNKNOWN:
+ return _(unknown reason);
+ case NM_VPN_CONNECTION_STATE_REASON_NONE:
+ return _(none);
+ case NM_VPN_CONNECTION_STATE_REASON_USER_DISCONNECTED:
+ return _(the user was disconnected);
+ case NM_VPN_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED:
+ return _(the base network connection was interrupted);
+ case NM_VPN_CONNECTION_STATE_REASON_SERVICE_STOPPED:
+ return _(the VPN service stopped unexpectedly);
+ case NM_VPN_CONNECTION_STATE_REASON_IP_CONFIG_INVALID:
+ return _(the VPN service returned invalid configuration);
+ case NM_VPN_CONNECTION_STATE_REASON_CONNECT_TIMEOUT:
+ return _(the connection attempt timed out);
+ case NM_VPN_CONNECTION_STATE_REASON_SERVICE_START_TIMEOUT:
+ return _(the VPN service did not start in time);
+ case NM_VPN_CONNECTION_STATE_REASON_SERVICE_START_FAILED:
+ return _(the VPN service failed to start);
+ case NM_VPN_CONNECTION_STATE_REASON_NO_SECRETS:
+ return _(no valid VPN secrets);
+ case NM_VPN_CONNECTION_STATE_REASON_LOGIN_FAILED:
+ return _(invalid VPN secrets);
+ case NM_VPN_CONNECTION_STATE_REASON_CONNECTION_REMOVED:
+ return _(the connection was removed);
+ default:
+ return _(unknown);
+ }
The above switch statement looks pretty comprehensive ! I wonder... what
ELSE could possibly be going wrong with my vpn connection attempt?
Im assuming maybe there are some directories or files whose permissions may
have recently been modified or corrupted... maybe there is a way to reset
my nmcli (or its config files, or whatever else may have suddenly gone
wrong) to previous settings?
--
Jay Vyas
http://jayunit100.blogspot.com
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: MM 0.6 conflicts with USB GPS device?
On Sat, 2013-06-01 at 17:24 +0200, W. Martin Borgert wrote: Quoting Dan Williams d...@redhat.com: Yeah, full debug output would be good then, since if MM sees that the device is not actually a modem, after probing it completely, it should never touch the device again unless the device goes away and re-appears. Here comes the normal and the debug log. You are right, that modem-manager does stop probing after some time, but this is after 55s, not 10s. The process does not respawn (PID stays the same), but does the AT+GCAP probe nine times with a distance between four and ten seconds. If there is a way to cut down the 55s more in the direction of 10s or 20s, this would be very helpful. Ok, the issue here is that after the first probe fails, MM should be smarter with plugins that require explicit probing (Iridium, Via CBP7). First, if the modem never replied with AT commands to anything, then there's no point in the other two plugins trying to probe. Second, these two plugins don't care about QCDM, so there's no point in having their probes also try QCDM. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: unknown reason error message in VPN connections
Hi Jay,
Would suggest running the plugin in debug mode and trying to troubleshoot
what actually happens. Which plugin is it anyway?
Scroll most of the way down on the following page and hopefully it'll give
us a direction:
https://live.gnome.org/NetworkManager/Debugging
Cheers,
Dan.
On Sun, Jun 2, 2013 at 2:17 AM, Jay Vyas jayunit...@gmail.com wrote:
Hi NM !
I'm using the Network Manager on RHEL, and have just found that VPN
stopped working with no meaningfull log messages.
I've posted the details here in case anyone wants points :) :) :)
http://superuser.com/questions/602490/network-connection-failed-unknown-reason
And also reposted them below so that a record of this thread will be on
the NM archives (im sure it might be useful to somebody, someday)...
down vote
favoritehttp://superuser.com/questions/602490/network-connection-failed-unknown-reason#
Im on RHEL, and found that my VPN stopped working.
I discovered that I could use the command line utility, nmcli, to try to
get more info about what was happening.
However, Im finding that the vpn still seems to fail and the error has no
clear meaning:
[jvyas@jvyas jvyas]# nmcli con up id X
Active connection state: unknown
Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/11
state: VPN connecting (need authentication) (2)
state: VPN connecting (3)
state: VPN connecting (getting IP configuration) (4)suggested tags:
vpnnetworkingwireless-networking
Error: Connection activation failed: unknown reason.
So , to try some googling - I found the switch statement that this error
message is being returned from, and it looks like most conditions are
handled pretty well, which means something very funny must be going wrong
when i try to connect to VPN:
+static const char *
+vpn_connection_state_reason_to_string (NMVPNConnectionStateReason reason)
+{
+ switch (reason) {
+ case NM_VPN_CONNECTION_STATE_REASON_UNKNOWN:
+ return _(unknown reason);
+ case NM_VPN_CONNECTION_STATE_REASON_NONE:
+ return _(none);
+ case NM_VPN_CONNECTION_STATE_REASON_USER_DISCONNECTED:
+ return _(the user was disconnected);
+ case NM_VPN_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED:
+ return _(the base network connection was interrupted);
+ case NM_VPN_CONNECTION_STATE_REASON_SERVICE_STOPPED:
+ return _(the VPN service stopped unexpectedly);
+ case NM_VPN_CONNECTION_STATE_REASON_IP_CONFIG_INVALID:
+ return _(the VPN service returned invalid configuration);
+ case NM_VPN_CONNECTION_STATE_REASON_CONNECT_TIMEOUT:
+ return _(the connection attempt timed out);
+ case NM_VPN_CONNECTION_STATE_REASON_SERVICE_START_TIMEOUT:
+ return _(the VPN service did not start in time);
+ case NM_VPN_CONNECTION_STATE_REASON_SERVICE_START_FAILED:
+ return _(the VPN service failed to start);
+ case NM_VPN_CONNECTION_STATE_REASON_NO_SECRETS:
+ return _(no valid VPN secrets);
+ case NM_VPN_CONNECTION_STATE_REASON_LOGIN_FAILED:
+ return _(invalid VPN secrets);
+ case NM_VPN_CONNECTION_STATE_REASON_CONNECTION_REMOVED:
+ return _(the connection was removed);
+ default:
+ return _(unknown);
+ }
The above switch statement looks pretty comprehensive ! I wonder... what
ELSE could possibly be going wrong with my vpn connection attempt?
Im assuming maybe there are some directories or files whose permissions
may have recently been modified or corrupted... maybe there is a way to
reset my nmcli (or its config files, or whatever else may have suddenly
gone wrong) to previous settings?
--
Jay Vyas
http://jayunit100.blogspot.com
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
