/usr/sbin/fwconsole userman --syncall -q

FreePBX
1

Hello

Freepbx 13.0.195.4
Asterisk 13.17.1

I have started getting emails from cron this morning saying there is a problem with userman and at the same time I see php is using 100% cpu,

Subject: Cron asterisk@astpbx /usr/sbin/fwconsole userman --syncall -q
Body:[Whoops\Exception\ErrorException]
posix_getpgid() expects parameter 1 to be long, string given
userman [–syncall] [–sync SYNC] [–force] [–list]

running top shows php using all cpu,

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
22583 asterisk 20 0 333m 5936 5724 R 100.0 0.6 75:24.12 php

I’ve tried running,

fwconsole ma install userman
fwconsole restart

Running from command line,
/usr/sbin/fwconsole userman --syncall -q

returns the same error as cron,

[Whoops\Exception\ErrorException]
posix_getpgid() expects parameter 1 to be long, string given

userman [–syncall] [–sync SYNC] [–force] [–list]

ps aux |grep php returns,

asterisk 22579 0.0 0.0 106060 760 ? Ss Sep03 0:00 /bin/sh -c [ -x /var/www/html/admin/modules/dashboard/scheduler.php ] && /var/www/html/admin/modules/dashboard/scheduler.php > /dev/null 2>&1
asterisk 22583 12.7 0.5 341332 5936 ? R Sep03 82:33 php /var/www/html/admin/modules/dashboard/scheduler.php

anyone know what is causing this?

Thanks,

2

php -v

3

[root@astpbx cron.d]# php -v
PHP 5.3.28 (cli) (built: Mar 31 2014 19:09:21)
Copyright © 1997-2013 The PHP Group
Zend Engine v2.3.0, Copyright © 1998-2013 Zend Technologies
with Zend Guard Loader v3.3, Copyright © 1998-2010, by Zend Technologies

4

This was corrected already, but I wanted to update the thread. It looks like pm2.log ballooned by 8GB overnight, which caused issues for /. After purging this and restarting again everything appears fine.

Since the restart, the log has stopped filling up with these,
PM2 log: App [ucpnode] with id [0] and pid [9539], exited with code [1] via signal [SIGINT]
PM2 log: Starting execution sequence in -fork mode- for app name:ucpnode id:0
PM2 log: App name:ucpnode id:0 online

5

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.