Mirakurun死なないでDVBチュナーをlockupさせる about mirakurun

[Corsaire01]

Seeing the numerous troubles I had, it seems that the heritage from the previous versions (using initd at the time) has gone quite heavy and triggered some obscure behavior.

So, I decided to clean wipe my system of all nodejs related files and packages and remake a clean install from scratch.
Now I do have what's expected with only one mirakurun-server process running, and being started from the sudoer user dedicated.

As such this bug can be closed.

[kanreisa]

please write in English.

[Corsaire01]

I added the English version

[kanreisa]

try below: (note: configurations are kept)

sudo -i
npm uninstall -g --unsafe mirakurun
pm2 unstartup
pm2 update
reboot

sudo -i
npm install -g --unsafe mirakurun
reboot

sudo -i
ps aux | grep PM2
pm2 status

• please tell me your platform which you're running
  https://github.com/Chinachu/Mirakurun/blob/master/.github/CONTRIBUTING.md#report-an-issue

• please paste the server/tuners configuration

[Corsaire01]

chinachu@goelette:~$ uname -a
Linux goelette 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

chinachu@goelette:~$ cat /etc/debian_version
stretch/sid

"/usr/local/etc/mirakurun/tuners.yml"

- name: PT3-S1
  types:
    - BS
    - CS
  command: recpt1 --device /dev/pt3video0 --lnb 15 <channel> - -
  decoder: arib-b25-stream-test
  isDisabled: false

- name: PT3-S2
  types:
    - BS
    - CS
  command: recpt1 --device /dev/pt3video1 --lnb 15 <channel> - -
  decoder: arib-b25-stream-test
  isDisabled: false

- name: PT3-T1
  types:
    - GR
  command: recpt1 --device /dev/pt3video2 <channel> - -
  decoder: arib-b25-stream-test
  isDisabled: false

- name: PT3-T2
  types:
    - GR
  command: recpt1 --device /dev/pt3video3 <channel> - -
  decoder: arib-b25-stream-test
  isDisabled: false

- name: TBS6922
  types:
    - SKY
  command: szap-s2j -c /usr/local/etc/szap-s2j.conf -l <satelite> -S 1 -p -r -M 5 -C 35 <channel>
  dvbDevicePath: /dev/dvb/adapter0/dvr0
  decoder: arib-b1-stream-test
  isDisabled: true

[Corsaire01]

I followed your instructions, there is the result

root@goelette:~# ps auxw | grep PM2
root       929  2.6  1.7 885328 35504 ?        Ssl  07:39   0:02 PM2 v2.6.1: God Daemon (/root/.pm2)

root@goelette:~# pm2 status
┌──────────────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬────────────┬──────┬──────────┐
│ App name         │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem        │ user │ watching │
├──────────────────┼────┼──────┼─────┼────────┼─────────┼────────┼─────┼────────────┼──────┼──────────┤
│ mirakurun-server │ 0  │ fork │ 943 │ online │ 0       │ 88s    │ 83% │ 117.8 MB   │ root │ disabled │
└──────────────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴────────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

[kanreisa]

pm2 delete mirakurun-server
pm2 save

[Corsaire01]

I'm confused here, I am supposed to do

pm2 delete mirakurun-server
pm2 save

after I did

sudo -i
npm install -g --unsafe mirakurun
reboot

?

[kanreisa]

pm2 delete and save are sudo too. you should clean up.

[Corsaire01]

But if I do this the process won't run anymore, right ?

[kanreisa]

your environment has broken. I did tested just now.

# pm2 status
│ chinachu-operator │ 1  │ ...
│ chinachu-wui      │ 0  │ ...

# npm install -g --unsafe mirakurun
# pm2 status
│ chinachu-operator │ 1  │ ...
│ chinachu-wui      │ 0  │ ...
│ mirakurun-server  │ 2  │ ...

# reboot
# pm2 status
│ chinachu-operator │ 1  │ ...
│ chinachu-wui      │ 0  │ ...
│ mirakurun-server  │ 2  │ ...

[Corsaire01]

Okay, things are getting more and more hairy...
Since the environment is broken I shutdown all processes and run npm install again... facing this error

root@goelette:~# npm install -g --unsafe mirakurun

> [email protected] preinstall /usr/local/lib/node_modules/.staging/mirakurun-d2df8319
> node bin/preinstall.js

/usr/local/bin/mirakurun -> /usr/local/lib/node_modules/mirakurun/bin/cli.sh
/usr/local/bin/mirakurun-epgdump -> /usr/local/lib/node_modules/mirakurun/bin/epgdump.js

> [email protected] postinstall /usr/local/lib/node_modules/mirakurun
> node bin/postinstall.js

Version: [email protected] [OK]
2.6.1-beta.1

Version: [email protected] [NG] Expected: >=2.4.0 <3.0.0
npm ERR! Linux 4.4.0-92-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "--unsafe" "mirakurun"
npm ERR! node v6.5.0
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE

npm ERR! [email protected] postinstall: `node bin/postinstall.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script 'node bin/postinstall.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mirakurun package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/postinstall.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs mirakurun
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mirakurun
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /root/npm-debug.log

[kanreisa]

ok, it's my mistake. I just released 2.6.1.

# npm install -g @kanreisa/[email protected]
# pm2 update
# npm install -g --unsafe mirakurun

[Corsaire01]

Okay this resolves the matter.

One thing however about the installation process, I start to see what is the real basis of the problem I had, PM2 processes are user separated.
It's not that my environment was broken, it is that I installed mirakurun being real root user, not by doing sudo.

# pm2 status
$ sudo pm2 status

doesn't show the same things

[Corsaire01]

Here I straight things up

# pm2 delete mirakurun-server
# pm2 kill
# pm2 unstartup
$ sudo npm install -g --unsafe mirakurun
$ sudo pm2 save
$ cd chinachu/
$ sudo pm2 start processes.json
$ sudo pm2 save

chinachu@goelette:~/chinachu$ sudo pm2 status
┌───────────────────┬────┬──────┬───────┬────────┬─────────┬────────┬─────┬────────────┬──────┬──────────┐
│ App name          │ id │ mode │ pid   │ status │ restart │ uptime │ cpu │ mem        │ user │ watching │
├───────────────────┼────┼──────┼───────┼────────┼─────────┼────────┼─────┼────────────┼──────┼──────────┤
│ chinachu-operator │ 2  │ fork │ 10901 │ online │ 0       │ 3m     │ 0%  │ 39.3 MB    │ root │ disabled │
│ chinachu-wui      │ 1  │ fork │ 10895 │ online │ 0       │ 3m     │ 0%  │ 143.9 MB   │ root │ disabled │
│ mirakurun-server  │ 0  │ fork │ 10839 │ online │ 1       │ 3m     │ 33% │ 599.2 MB   │ root │ disabled │
└───────────────────┴────┴──────┴───────┴────────┴─────────┴────────┴─────┴────────────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

[kanreisa]

it is same.

please don't ask me more about PM2. go here.