cloud9 in responding on 2018-04-22 buster image

[Mark A. Yoder]

I've just downloaded https://rcn-ee.com/rootfs/bb.org/testing/2018-04-22/buster-iot/bone-debian-buster-iot-armhf-2018-04-22-4gb.img.xz and booted it up.

Everything seems to be running fine, but cloud9 isn't responding on port 3000.  In fact, I'm not getting a response on port 80 either.

systemctl status cloud9

● cloud9.service - Cloud9 IDE

   Loaded: loaded (/lib/systemd/system/cloud9.service; static; vendor preset: enabled)

   Active: active (running) since Mon 2018-04-23 16:36:53 EDT; 4s ago

  Process: 6153 ExecStartPre=/opt/cloud9/cloud9-symlink (code=exited, status=0/SUCCESS)

 Main PID: 6159 (nodejs)

    Tasks: 6 (limit: 1032)

   Memory: 7.5M

   CGroup: /system.slice/cloud9.service

           └─6159 /usr/bin/nodejs server.js --packed -w /var/lib/cloud9

Apr 23 16:36:53 beaglebone systemd[1]: Starting Cloud9 IDE...

Apr 23 16:36:53 beaglebone systemd[1]: Started Cloud9 IDE.

Apr 23 16:36:56 beaglebone cloud9ide[6159]: Starting standalone

It seems to be running...

sudo ./version.sh 

git:/opt/scripts/:[871a0ada4779d046081f2b29f4a95d44db2f954d]

eeprom:[A335BNLT0A5C3513BBBK3281]

model:[TI_AM335x_BeagleBone_Black]

dogtag:[BeagleBoard.org Debian Image 2018-04-22]

bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.03-00002-gac9cce7c6a]:[location: dd MBR]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2016.03-00001-g9a81f4a]:[location: dd MBR]

kernel:[4.14.35-ti-r44]

nodejs:[v8.11.1]

uboot_overlay_options:[enable_uboot_overlays=1]

uboot_overlay_options:[disable_uboot_overlay_audio=1]

uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]

uboot_overlay_options:[enable_uboot_cape_universal=1]

pkg:[bb-cape-overlays]:[4.4.20180412.0-0rcnee0~buster+20180412]

pkg:[bb-wl18xx-firmware]:[1.20180328-0rcnee2~buster+20180328]

pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~buster+20180328]

groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]

cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet]

dmesg | grep pinctrl-single

[    1.072466] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568

dmesg | grep gpio-of-helper

[    1.079165] gpio-of-helper ocp:cape-universal: ready

END

--Mark

[Robert Nelson]

On Mon, Apr 23, 2018 at 3:39 PM, Mark A. Yoder <mark.a...@gmail.com> wrote:
> I've just downloaded
> https://rcn-ee.com/rootfs/bb.org/testing/2018-04-22/buster-iot/bone-debian-buster-iot-armhf-2018-04-22-4gb.img.xz
> and booted it up.
>
> Everything seems to be running fine, but cloud9 isn't responding on port
> 3000. In fact, I'm not getting a response on port 80 either.
>
> systemctl status cloud9
> ● cloud9.service - Cloud9 IDE
> Loaded: loaded (/lib/systemd/system/cloud9.service; static; vendor
> preset: enabled)
> Active: active (running) since Mon 2018-04-23 16:36:53 EDT; 4s ago
> Process: 6153 ExecStartPre=/opt/cloud9/cloud9-symlink (code=exited,
> status=0/SUCCESS)
> Main PID: 6159 (nodejs)
> Tasks: 6 (limit: 1032)
> Memory: 7.5M
> CGroup: /system.slice/cloud9.service
> └─6159 /usr/bin/nodejs server.js --packed -w /var/lib/cloud9
>
> Apr 23 16:36:53 beaglebone systemd[1]: Starting Cloud9 IDE...
> Apr 23 16:36:53 beaglebone systemd[1]: Started Cloud9 IDE.
> Apr 23 16:36:56 beaglebone cloud9ide[6159]: Starting standalone
>
> It seems to be running...

With buster, we are trying out "nginx", the server config has this setup:

location / {
#Cloud9
proxy_pass http://127.0.0.1:3000;
}

location /bone101 {
proxy_pass http://127.0.0.1:8000;
}

location /nodered {
proxy_pass http://127.0.0.1:1880;
}

thus http://beaglebone.local/ should be -> cloud9.. unless something
else broke...

>
> sudo ./version.sh
> git:/opt/scripts/:[871a0ada4779d046081f2b29f4a95d44db2f954d]
> eeprom:[A335BNLT0A5C3513BBBK3281]
> model:[TI_AM335x_BeagleBone_Black]



> dogtag:[BeagleBoard.org Debian Image 2018-04-22]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
> 2018.03-00002-gac9cce7c6a]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2016.03-00001-g9a81f4a]:[location: dd MBR]

PS, 2016.03 in eMMC is going to mess things up..

> kernel:[4.14.35-ti-r44]
> nodejs:[v8.11.1]
> uboot_overlay_options:[enable_uboot_overlays=1]
> uboot_overlay_options:[disable_uboot_overlay_audio=1]
> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
> uboot_overlay_options:[enable_uboot_cape_universal=1]
> pkg:[bb-cape-overlays]:[4.4.20180412.0-0rcnee0~buster+20180412]
> pkg:[bb-wl18xx-firmware]:[1.20180328-0rcnee2~buster+20180328]
> pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~buster+20180328]
> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
> plugdev users systemd-journal bluetooth netdev i2c cloud9ide gpio pwm eqep
> admin spi tisdk weston-launch xenomai]
> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
> root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
> net.ifnames=0 quiet]
> dmesg | grep pinctrl-single
> [ 1.072466] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size
> 568
> dmesg | grep gpio-of-helper
> [ 1.079165] gpio-of-helper ocp:cape-universal: ready
> END

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Robert Nelson]

On Mon, Apr 23, 2018 at 3:48 PM, Robert Nelson <robert...@gmail.com> wrote:
> On Mon, Apr 23, 2018 at 3:39 PM, Mark A. Yoder <mark.a...@gmail.com> wrote:
>> I've just downloaded
>> https://rcn-ee.com/rootfs/bb.org/testing/2018-04-22/buster-iot/bone-debian-buster-iot-armhf-2018-04-22-4gb.img.xz
>> and booted it up.
>>
>> Everything seems to be running fine, but cloud9 isn't responding on port
>> 3000. In fact, I'm not getting a response on port 80 either.
>>
>> systemctl status cloud9
>> ● cloud9.service - Cloud9 IDE
>> Loaded: loaded (/lib/systemd/system/cloud9.service; static; vendor
>> preset: enabled)
>> Active: active (running) since Mon 2018-04-23 16:36:53 EDT; 4s ago
>> Process: 6153 ExecStartPre=/opt/cloud9/cloud9-symlink (code=exited,
>> status=0/SUCCESS)
>> Main PID: 6159 (nodejs)
>> Tasks: 6 (limit: 1032)
>> Memory: 7.5M
>> CGroup: /system.slice/cloud9.service
>> └─6159 /usr/bin/nodejs server.js --packed -w /var/lib/cloud9
>>
>> Apr 23 16:36:53 beaglebone systemd[1]: Starting Cloud9 IDE...
>> Apr 23 16:36:53 beaglebone systemd[1]: Started Cloud9 IDE.
>> Apr 23 16:36:56 beaglebone cloud9ide[6159]: Starting standalone
>>
>> It seems to be running...

no it looks like cloud9 needs to be rebuilt:

Apr 23 21:29:53 beaglebone systemd[1]: cloud9.service: Main process
exited, code=killed, status=6/ABRT
Apr 23 21:29:53 beaglebone systemd[1]: cloud9.service: Failed with
result 'signal'.
Apr 23 21:29:53 beaglebone systemd[1]: Starting Cloud9 IDE...
Apr 23 21:29:53 beaglebone systemd[1]: Started Cloud9 IDE.
Apr 23 21:29:54 beaglebone cloud9ide[1805]: Starting standalone
Apr 23 21:29:55 beaglebone cloud9ide[1805]: LISTEN_FDS = 1
Apr 23 21:29:55 beaglebone cloud9ide[1805]: /usr/bin/nodejs[1805]:
../src/pipe_wrap.cc:131:static void node::PipeWrap::New(const
v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[0]->IsInt32()'
failed.

[Robert Nelson]

rebuilding the nodejs package:

Apr 24 16:08:45 beaglebone cloud9ide[1746]: /usr/bin/nodejs[1746]:

[Robert Nelson]

@mark - fix seems to be here:

https://github.com/rubenv/node-systemd/pull/15

Testing. ;)