1.5.3


Old Stuff

 www.your-freedom.net
 www.secure-tunnel.com

Ticket #68 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Gets into state where it can't be stopped or started

Reported by: david at colettas dot org Assigned to: andrei
Priority: normal Milestone: AlmostVPN 0.9.5
Component: PreferencePanel Version: 0.9
Severity: normal Keywords:
Cc:

Description

Since the fix to ticket 59 (0.93) I find that AlmostVPN will get into a state where it is trying to start the session but can't. The start button is disabled. All I can do to get it working again is to reboot.

This seems to happen sometimes but not all the time after the Mac awakens from sleep. Sometimes the Mac is connecting to a different network after awakening, but I have seen it happen even when it is connecting to the same network after awakening.

Here's what I see in the console: 2005-11-16 09:05:11.305 System Preferences[211] retrivePasswordOfType : Fail to locate password almostVPN@almostVPN/ - error Mac OS error -25300 2005-11-16 09:05:12.003 almostVPNTool[302] retrivePasswordOfType : Fail to locate password almostVPN@almostVPN/ - error Mac OS error -25300 Password: 2005-11-16 09:05:12.183 defaults[303] There is no (LoginHook?) default for the (com.apple.loginwindow) domain. Defaults have not been changed. 2005-11-16 09:05:13.071 almostVPNTool[304] retrivePasswordOfType : Fail to locate password almostVPN@almostVPN/ - error Mac OS error -25300

P.S. Ticket 59 seems to be fixed! Thanks!

Attachments

logs.zip (2.4 kB) - added by rnapier@employees.org on 11/25/05 10:47:13.
Sample of logs and status

Change History

11/16/05 11:40:10 changed by andrei

  • status changed from new to assigned.
  • version set to 0.9.
  • component changed from FAQ to PreferencePanel.
  • milestone set to AlmostVPN 0.9.4.

When it happen next time, could you please save

  • ~/Library/Applications Support/AlmostVPN/almostvpn.log and
  • ~/Library/Applications Support/AlmostVPN/almostvpn.status

and either e-mail them to me or (better) attache them to this ticket.

Meanwhile, you do not have to reboot to restore your system. it should be enough to kill ssh command. 

ps -ax | grep ssh

should give you list of all ssh processes running on the box (most likely you will have only one). First number is "PID" of the process 

kill <put PID of the process here>

will kill the process. Alternatively you can use 

killall ssh

it will kill all processes with name like "*ssh*". If you will get message about "Operation not permitted" (though you should not), you can use sudo to run these commands as root.

PS Good to hear confirmation about #59 PPS You can ignore messages about almostVPN@almostVPN. They are completely none-fatal and as a mater of fact already removed from the future builds.

11/25/05 10:47:13 changed by rnapier@employees.org

  • attachment logs.zip added.

Sample of logs and status

11/25/05 10:47:34 changed by rnapier@employees.org

I believe I am seeing the same behavior after a resume from sleep. There are no "SSH" processes running. I've attached the log and status files below. If I click on "Start" nothing happens except the Start button grays and I get a "Starting Profile" message. I can click the lock to the left of Start twice and the Start button will become active again, but it never makes the connection.

I have the password set to "@ask@" so I should see an almost immediate password request box which I don't.

11/28/05 22:49:08 changed by andrei

  • milestone changed from AlmostVPN 0.9.4 to AlmostVPN 0.9.5.

I hope I did fix this one. Will not close this ticket for a while, to make sure that I really did fix it. Fix will be part of 0.9.5 due Nov 29th

12/06/05 10:37:06 changed by andrei

  • status changed from assigned to closed.
  • resolution set to fixed.

It looks like this one is fixed. Will close it now.