socat using 100% of CPU

Bug #1518140 reported by map7
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Epoptes
Invalid
Undecided
Unassigned
socat (Debian)
Unknown
Unknown
socat (Ubuntu)
Confirmed
Critical
Unassigned

Bug Description

I'm using Epoptes version 0.5.7-1 & socat 1.7.3.0-1 on Debian Testing and when I boot I'm getthign a process which continues to use 100% of CPU forever until I kill it.

3128 ? R 11131:48 socat openssl-connect:server:789,cafile=/etc/epoptes/server.crt,interval=60,forever EXEC:bash -c \"exec -a epoptes-client sh\"

Revision history for this message
Laércio de Sousa (lbssousa) wrote : Re: [Bug 1518140] [NEW] socat using 100% of CPU

Try to set manually the IP address of your Epoptes server in /etc/default/epoptes-client. It may be a problem related to server name resolution.

Enviado através do Boxer

Em 19/11/2015 11:05 PM, map7 <email address hidden> escreveu:

Public bug reported:

I'm using Epoptes version 0.5.7-1 & socat 1.7.3.0-1 on Debian Testing
and when I boot I'm getthign a process which continues to use 100% of
CPU forever until I kill it.

3128 ? R 11131:48 socat openssl-
connect:server:789,cafile=/etc/epoptes/server.crt,interval=60,forever
EXEC:bash -c \"exec -a epoptes-client sh\"

** Affects: epoptes
     Importance: Undecided
         Status: New

--
You received this bug notification because you are subscribed to
Epoptes.
https://bugs.launchpad.net/bugs/1518140

Title:
  socat using 100% of CPU

Status in Epoptes:
  New

Bug description:
  I'm using Epoptes version 0.5.7-1 & socat 1.7.3.0-1 on Debian Testing
  and when I boot I'm getthign a process which continues to use 100% of
  CPU forever until I kill it.

  3128 ? R 11131:48 socat openssl-
  connect:server:789,cafile=/etc/epoptes/server.crt,interval=60,forever
  EXEC:bash -c \"exec -a epoptes-client sh\"

To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/1518140/+subscriptions

Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

Hi, as the bug title says, it's a problem with socat, not with epoptes.
We cannot solve it in the epoptes code.

We've had reported it in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803378, you can comment there to show that it's important to you, so that the socat debian maintainers backport the patch that the upstream developer supplied.

Changed in epoptes:
status: New → Invalid
Changed in socat (Ubuntu):
importance: Undecided → Critical
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.