SYSTEM WARNING: 'file_get_contents(): SSL: Connection reset by peer' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

SYSTEM WARNING: 'file_get_contents(): Failed to enable crypto' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

SYSTEM WARNING: 'file_get_contents(https://www.clearos.com/?rendertype=json&get=header): failed to open stream: operation failed' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

Anonymous | Login

2024-05-05 07:35 MDT

Project: All Projects ClearCenter ClearOS

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
0008651	ClearOS	syswatch	public	2016-05-10 13:37	2016-06-20 09:42
Reporter	user2
Assigned To	user2
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version	6.7.0
Target Version	6.7.0 Updates	Fixed in Version	6.7.0 Updates
Summary	0008651: Extra PPPoE kill is not selective enough - ClearOS 6
Description	PPPoE connections can sometimes lock PPP devices which causes a gentle "ifdown pppX" to no longer function. Syswatch comes a long and kills the pppd/pppoe process, but the regex for determining the process ID is lame. Tighten it up.
Tags	No tags attached.
Attached Files

Relationships

related to  0008641 closed user2  Extra PPPoE kill is not selective enough

Relationships

Notes

There are no notes attached to this issue.

Notes

Issue History
Date Modified	Username	Field	Change
2016-05-10 13:37	user2	New Issue
2016-05-10 13:37	user2	Issue generated from: 0008641
2016-05-10 13:37	user2	Relationship added	related to 0008641
2016-05-11 11:45	user2	Status	new => confirmed
2016-05-11 11:45	user2	Target Version	6.7.0 Updates => 6.8.0 Beta 1
2016-05-25 08:08	user2	Target Version	6.8.0 Beta 1 => 6.7.0 Updates
2016-05-25 08:15	user2	Status	confirmed => resolved
2016-05-25 08:15	user2	Fixed in Version	=> 6.7.0 Updates
2016-05-25 08:15	user2	Resolution	open => fixed
2016-05-25 08:15	user2	Assigned To	=> user2
2016-06-20 09:42	user2	Status	resolved => closed

Issue History