crond runs "cmd service start_vpnserver1" every minute

[Stobber]

I'm running 380.65 on an RT-N66U with one OVPN server enabled (and no clients). I'm not sure whether this is a bug or not, but I noticed this in my syslog:

Feb 23 10:52:00 crond[234]: USER admin pid 761 cmd service start_vpnserver1
Feb 23 10:52:00 rc_service: service 762:notify_rc start_vpnserver1
Feb 23 10:52:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...
Feb 23 10:53:00 crond[234]: USER admin pid 766 cmd service start_vpnserver1
Feb 23 10:53:00 rc_service: service 767:notify_rc start_vpnserver1
Feb 23 10:53:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...
Feb 23 10:54:00 crond[234]: USER admin pid 769 cmd service start_vpnserver1
Feb 23 10:54:00 rc_service: service 770:notify_rc start_vpnserver1
Feb 23 10:54:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...
Feb 23 10:55:00 crond[234]: USER admin pid 774 cmd service start_vpnserver1
Feb 23 10:55:00 rc_service: service 775:notify_rc start_vpnserver1
Feb 23 10:55:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...
Feb 23 10:55:39 miniupnpd[621]: upnp_event_recv: recv(): Connection reset by peer
Feb 23 10:56:00 crond[234]: USER admin pid 779 cmd service start_vpnserver1
Feb 23 10:56:00 rc_service: service 780:notify_rc start_vpnserver1
Feb 23 10:56:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...
Feb 23 10:57:00 crond[234]: USER admin pid 784 Cron
Feb 23 10:57:00 rc_service: service 785:notify_rc start_vpnserver1
Feb 23 10:57:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...
Feb 23 10:58:00 crond[234]: USER admin pid 787 cmd service start_vpnserver1
Feb 23 10:58:00 rc_service: service 788:notify_rc start_vpnserver1
Feb 23 10:58:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...
Feb 23 10:59:00 crond[234]: USER admin pid 795 cmd service start_vpnserver1
Feb 23 10:59:00 rc_service: service 796:notify_rc start_vpnserver1
Feb 23 10:59:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...
Feb 23 11:00:00 crond[234]: USER admin pid 811 cmd service start_vpnserver1
Feb 23 11:00:00 rc_service: service 812:notify_rc start_vpnserver1
Feb 23 11:00:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...

What's that about? Why not just start the service once and let it be? Is it crashing repeatedly without logging an error? If having cron start it every minute is a workaround for a bug, why not silence output for this job?

 

[joegreat]

Really?? You want to restart the VPN server silently every minute???

<helpful>

Show us the output of the Telnet command: cru -l

And check who is setting this crazy schedule with: grep -r cru /jffs/scripts/*​

</helpful>

With more input, much more input Johnny 5 might be able to help!

 

[Stobber]

Huh? You're a "very senior member" so I'm surprised you would post something so unhelpful. Mind explaining what you mean, or helping me understand why there's an attempt to restart the server every minute in the first place? I'm honestly just trying to figure out whether this is a bug that should be reported or just something I don't understand.

 

[joegreat]

Huh? You're a "very senior member" so I'm surprised you would post something so unhelpful.

The help is in the two middle lines - and the fun around it (which was clearly not understood ).

 

[john9527]

I'm running 380.65 on an RT-N66U with one OVPN server enabled (and no clients). I'm not sure whether this is a bug or not, but I noticed this in my syslog:

Feb 23 10:52:00 crond[234]: USER admin pid 761 cmd service start_vpnserver1
Feb 23 10:52:00 rc_service: service 762:notify_rc start_vpnserver1
Feb 23 10:52:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...
Feb 23 10:53:00 crond[234]: USER admin pid 766 cmd service start_vpnserver1
Feb 23 10:53:00 rc_service: service 767:notify_rc start_vpnserver1
Feb 23 10:53:00 syslog: VPN_LOG_NOTE: 682: VPN Server 1 already running...


What's that about? Why not just start the service once and let it be? Is it crashing repeatedly without logging an error? If having cron start it every minute is a workaround for a bug, why not silence output for this job?

That's what happens if you set the 'Poll Interval' to 1 minute on the VPN client or server page (the default is 0=disabled).