Modify

Ticket #2508 (closed defect: invalid)

Opened 3 years ago

Last modified 2 years ago

ebox-pwdsync-server uses all available CPU

Reported by: anonymous Owned by: cperez@…
Milestone: 2.0.X Component: users
Severity: normal Keywords:
Cc: zentyal@…

Description

I have a test Zentyal setup which I have configured for AD sync. Maybe it's because I'm not using the password sync client but ebox-pwdsync-server constantly respawns and uses all available CPU. It seems pretty hard core for something that should just be sitting there and wait for a connection...

Attachments

Change History

comment:1 Changed 3 years ago by jacalvo@…

  • Status changed from new to closed
  • Resolution set to worksforme

If it's constantly respawning that's because it's crashing. The normal functioning is just waiting for a connection as you say.

But we can't reproduce it. Maybe there is something wrong with your configuration.

Could you provide us more information?

Maybe you can see some error if you execute it manually with:

stop ebox.ad-pwdsync /usr/share/ebox-usersandgroups/ebox-pwdsync-server

comment:2 Changed 3 years ago by jacalvo@…

Sorry, I meant two separate commands.

First:

stop ebox.ad-pwdsync

And then:

/usr/share/ebox-usersandgroups/ebox-pwdsync-server

(both with root (sudo) permissions)

comment:3 Changed 2 years ago by zentyal@…

  • Cc zentyal@… added
  • priority changed from normal to high
  • Status changed from closed to reopened
  • Resolution worksforme deleted

:~$ sudo stop ebox.ad-pwdsync [sudo] password for sysadmin: ebox.ad-pwdsync stop/waiting :~$ sudo /usr/share/ebox-usersandgroups/ebox-pwdsync-server wrong key length: key must be 128, 192 or 256 bits long at /usr/share/ebox-usersandgroups/ebox-pwdsync-server line 53, <GEN1> line 60

comment:4 Changed 2 years ago by jacalvo@…

  • Status changed from reopened to closed
  • Resolution set to invalid

Your configuration is wrong, as it is said on the documentation:

 http://trac.zentyal.org/wiki/Document/Documentation/EBoxActiveDirectorySync

"As Secret key you can choose any password as long as it has 16 characters."

You have set a password with a different size than 16 characters, that's why it's constantly crashing (being restarted by upstart actually).

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.