ppss makes some progress and then locks up

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install ppss version 2.85 on ubuntu lucid
2. Run it with sufficient load (I tried 1645 tasks, 10 threads)
3. Observe it to process several tasks (I got 18-40) and then nothing happens.

What version of the product are you using? On what operating system?
Ubuntu lucid (10.04). The machine is LXC container (not sure if that mattes).

Please provide any additional information below.
If I run the ppss with "bash -x", the several last lines are:
++ date '+%b %d %H:%M:%S'
+ DATE='Aug 11 23:52:11'
+ PREFIX='Aug 11 23:52:11: DEBUG'
+ PREFIX_SMALL='Aug 11 23:52:11: '
+ '[' '!' DEBUG = ERROR ']'
+ ECHO_MSG='Aug 11 23:52:11:  Item is a directory or is empty.'
+ LOG_MSG='Aug 11 23:52:11: DEBUG Item is a directory or is empty.'
+ '[' '!' -z '' ']'
+ '[' DEBUG == INFO ']'
+ '[' DEBUG == ERROR ']'
+ '[' DEBUG == WARN ']'
+ '[' DEBUG == DSPLY ']'
+ '[' DEBUG == DSPLY ']'
+ '[' DEBUG == ERROR ']'
+ '[' DEBUG == WARN ']'
+ '[' DEBUG == ERROR ']'
+ '[' DEBUG == PRCNT ']'
+ return 0
+ read event

Original issue reported on code.google.com by skliarie@gmail.com on 11 Aug 2011 at 7:52

[GoogleCodeExporter]

The thread says that inotify is not supported by cgroup and thus LXC:
http://www.mail-archive.com/lxc-devel@lists.sourceforge.net/msg00966.html

I tried to run the spss script with --disable-inotify with the same result.

Original comment by skliarie@gmail.com on 11 Aug 2011 at 8:02

[GoogleCodeExporter]

If I run the ppss on a directory, then it works properly:
 ppss -d . -c '/tmp/a.sh' 
It I run the ppss on a file that is not in the current directory (used both 
relative and full path) - it gets stuck.
 ppss -f ../work_queue -c '/tmp/a.sh' 
If I run the ppss on a file that sits in the current directory - then it works 
properly...

Very, very weird...

Original comment by skliarie@gmail.com on 11 Aug 2011 at 8:12

[GoogleCodeExporter]

That is very strange as PPSS actually has problems running on the current 
directory as it also stores it's ppss_dir working directory there and it will 
start processing it's own files. I may have to provide some kind of exclude 
filter for this, but that's another story. 

Thanks for the report. This is a strange issue. 

Can you test this issue on 'real' hardware and see if it makes any difference?

Original comment by Louwrentius on 17 Aug 2011 at 10:30

[GoogleCodeExporter]

Sorry, I can't...

Original comment by skliarie@gmail.com on 18 Aug 2011 at 2:51

[GoogleCodeExporter]

Original comment by Louwrentius on 25 Dec 2011 at 4:40

• Changed state: Invalid