| Anonymous | Login | 2024-12-22 00:14 MST |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0000676 | ClearCenter | app-dynamic-vpn - Dynamic VPN | public | 2012-07-06 20:11 | 2012-09-04 14:20 | ||||
| Reporter | bchambers | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 6.2.0 | ||||||||
| Target Version | 6.3.0 | Fixed in Version | 6.2.0 Updates | ||||||
| Summary | 0000676: vpnwatchd doesn't start automatically | ||||||||
| Description | In setting up a managed dynamic VPN, the tunnel was failing to come up. On inspection, the vpnwatchd daemon was stopped. Starting it, and running chkconfig vpnwatchd on fixes the issue. This was was instance...Have not attempted to reproduce. What starts the vpnwatchd and sets chkconfig? Should it not start when Dynamic VPN app is installed? | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0000540) bchambers (administrator) 2012-07-06 20:26 |
Another support ticket with same issue...vpnwatchd was not started on two 6.2 servers. This bug is confirmed. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-07-06 20:11 | bchambers | New Issue | |
| 2012-07-06 20:11 | bchambers | Status | new => assigned |
| 2012-07-06 20:11 | bchambers | Assigned To | => user2 |
| 2012-07-06 20:26 | bchambers | Note Added: 0000540 | |
| 2012-07-17 13:31 | user2 | Status | assigned => resolved |
| 2012-07-17 13:31 | user2 | Fixed in Version | => 6.2.0 Updates |
| 2012-07-17 13:31 | user2 | Resolution | open => fixed |
| 2012-09-04 14:20 | user2 | Status | resolved => closed |
|
Issue History |