search

fossology / fossology

FOSSology is an open source license compliance software system and toolkit. As a toolkit you can run license, copyright and export control scans from the command line. As a system, a database and web ui are provided to give you a compliance workflow. License, copyright and export scanners are tools used in the workflow.
https://fossology.github.io/
GNU General Public License v2.0
800 stars 417 forks source link

scheduler startup tests fail inconsistently on multiserver installations #34

Open bobgob opened 9 years ago

bobgob commented 9 years ago

I have observed this on two multi server installations (fossologyitg.fc and fossology.fc). When the scheduler starts and runs the startup tests on the agent machines, some of the tests fail. Restarting the scheduler will result in different failures (or all successful). In the example below, all tests passed after a scheduler restart.

For example: '2014-12-16 09:37:24 scheduler [2080] :: NOTE: * 2014-12-16 09:37:24 scheduler [2080] :: NOTE: * FOSSology scheduler started * 2014-12-16 09:37:24 scheduler [2080] :: NOTE: * pid: 2081 * 2014-12-16 09:37:24 scheduler [2080] :: NOTE: * verbose: 1 * 2014-12-16 09:37:24 scheduler [2080] :: NOTE: * config: /etc/fossology * 2014-12-16 09:37:24 scheduler [2080] :: NOTE: * 2014-12-16 09:37:25 scheduler [2080] :: JOB[-15].nomos[2112.foitgagent1]: agent failed, code: 251 2014-12-16 09:37:25 scheduler [2080] :: ERROR agent.c.957: agent foitgagent1.nomos has failed scheduler startup test 2014-12-16 09:37:25 scheduler [2080] :: ERROR agent.c.300: agent foitgagent1.nomos has been invalidated, removing from agents 2014-12-16 09:37:25 scheduler [2080] :: JOB[-15].nomos[2112.foitgagent1]: agent didn't send version information: "FATAL libfossscheduler.c.128: unable to insert into agent table: ERROR: duplicate key value violates unique constraint "agent_unique_name_rev"" 2014-12-16 09:37:25 scheduler [2080] :: ERROR agent.c.300: agent foitgagent1.mimetype has been invalidated, removing from agents 2014-12-16 09:37:25 scheduler [2080] :: JOB[-11].mimetype[2107.foitgagent1]: agent didn't send version information: "FATAL libfossscheduler.c.128: unable to insert into agent table: ERROR: duplicate key value violates unique constraint "agent_unique_name_rev"" 2014-12-16 09:37:25 scheduler [2080] :: JOB[-11].mimetype[2107.foitgagent1]: agent was killed by signal: 9.Killed 2014-12-16 09:37:25 scheduler [2080] :: ERROR agent.c.957: agent foitgagent1.mimetype has failed scheduler startup test '

mcjaeger commented 9 years ago

I am not sure if I am the best person to test multi server. Any updates on the issue? I am setting this to 3.0.1 if that remains unconfirmed.

mcjaeger commented 9 years ago

We are not working with the Multiserver setup? Would ther be any persons org that have expereince with this?

It seems like an older issue and therefore I wondering if there are any serious issues still open?

mcjaeger commented 6 years ago

could be relevant if someone tries to do multiserver with docker

GMishx commented 6 years ago

As per your log

2014-12-16 09:37:25 scheduler [2080] :: JOB[-15].nomos[2112.foitgagent1]: agent didn't send version information: "FATAL libfossscheduler.c.128: unable to insert into agent table: ERROR: duplicate key value violates unique constraint "agent_unique_name_rev""

There is a duplication of agent name and revision. Can you please check the DB and try restarting the scheduler?