Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Can't install on 2.90~10 #17

Open
SergioRius opened this issue Jun 4, 2022 · 5 comments
Open

Can't install on 2.90~10 #17

SergioRius opened this issue Jun 4, 2022 · 5 comments

Comments

@SergioRius
Copy link

I had previously updated to 2.90~10 (large) thus loosing all the mods.
Today I tried to reinstall the SetupHelper using the manual procedure but there's some problem with PackageManager and the install seems not functional.

root@einstein:/data# wget -qO - https://github.com/kwindrem/SetupHelper/archive/latest.tar.gz | tar -xzf - -C /data
root@einstein:/data# mv /data/SetupHelper-latest /data/SetupHelper
root@einstein:/data# /data/SetupHelper/setup
creating root setup options directory /data/setupOptions
creating package options directory /data/setupOptions/SetupHelper
creating file set for v2.90~10

This package provides support functions and utilities for Venus modification packages
Packages are automatically reinstalled following a Venus OS update
All actions are controlled via /Settings/PackageMonitor in the GUI
  Packages may be automatically updated from GitHub or a USB stick
  Previously uninstalled packages can also be downloaded an installed


Available actions:
  Install and activate (i)
  Reinstall (r) based on options provided at last install
  Uninstall (u) and restores all files to stock
  Quit (q) without further action
  Display setup log (s) outputs the last 100 lines of the log

Choose an action from the list above: i
installing PackageManager service
svc: warning: unable to chdir to /service/PackageManager: file does not exist
adding SetupHelper/setup to reinstallScriptsList
adding SetupHelper reinstall script to /data/rcS.local
Restart the GUI now (y) or issue a do it manually later (n): y
restarting GUI ...
root@einstein:/data#

root@einstein:/data/SetupHelper# ./setup

This package provides support functions and utilities for Venus modification packages
Packages are automatically reinstalled following a Venus OS update
All actions are controlled via /Settings/PackageMonitor in the GUI
  Packages may be automatically updated from GitHub or a USB stick
  Previously uninstalled packages can also be downloaded an installed


Available actions:
  Install and activate (i)
  Reinstall (r) based on options provided at last install
  Uninstall (u) and restores all files to stock
  Quit (q) without further action
  Display setup log (s) outputs the last 100 lines of the log

Choose an action from the list above: i
restarting PackageManager service
svc: warning: unable to chdir to /service/PackageManager: file does not exist
svc: warning: unable to chdir to /service/PackageManager/log: file does not exist
svc: warning: unable to chdir to /service/PackageManager: file does not exist
svc: warning: unable to chdir to /service/PackageManager/log: file does not exist
completed
root@einstein:/data/SetupHelper# ll service
drwxrwxr-x    3 root     root        4.0K May  4 23:17 .
drwxrwxr-x    5 root     root        4.0K May  4 23:17 ..
drwxrwxr-x    2 root     root        4.0K May  4 23:17 log
-rw-rw-r--    1 root     root        6.0K May  4 23:17 .DS_Store
-rwxrwxr-x    1 root     root          62 May  4 23:17 run
root@einstein:/data/SetupHelper#
@kwindrem
Copy link
Owner

kwindrem commented Jun 5, 2022

I can not explain what is going on.

/service/PackageManager should be created during SetupHelper install and the "installing PackageManager service" is output just before that happens. The second setup shows "reinstalling PackageManager service" indicating that the first install at least partially created it. but the chdir errors indicate that /service/PackageManager probably doesn't exist. You could check the /service directory to see if it does.

In Venus OS v2.90, /run/overlays/service is mounted on top of /service. This is done because the root file system is mounted read-only. (SetupHelper remounts rootfs read-write for other reasons so this is redundant.)

@jsalbre
Copy link

jsalbre commented Jun 5, 2022 via email

@kwindrem
Copy link
Owner

kwindrem commented Jun 5, 2022

I tried a manual instal on v2.90~10 large (although the version info doesn't indicate large) and SetupHelper installed and PackageManager started.

I did get an error "svc: warning: unable to control /service/PackageManager: file does not exist" but everything was working.

I'll look into the error.

To be clear, I did not get the chdir warning and PackageManager was running.

@kwindrem
Copy link
Owner

kwindrem commented Jun 5, 2022

The errors appear to be due to a timing issue. The next release of SetupHelper will include delays while installing a service to prevent the errors.

@SergioRius
Copy link
Author

The errors appear to be due to a timing issue. The next release of SetupHelper will include delays while installing a service to prevent the errors.

You're the boss. I didn't even had time to receive the github notification and check the /service folder.
BTW, FWIW:

root@einstein:~# ll /service
drwxr-xr-x   51 root     root        1.1K Jun  4 16:15 .
drwxr-xr-x   20 root     root        4.0K May 24 14:24 ..
drwxr-xr-x    4 root     root         120 May 24 19:36 can-bus-bms.can0
drwxr-xr-x    4 root     root         120 May 24 19:36 can-bus-bms.can1
drwxr-xr-x    4 root     root         100 May 24 19:36 dbus-adc
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-ble-sensors
drwxr-xr-x    4 root     root         100 May 24 19:36 dbus-digitalinputs
drwxr-xr-x    4 root     root         100 May 24 19:36 dbus-fronius
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-generator-starter
drwxr-xr-x    4 root     root         100 May 24 19:36 dbus-modbus-client
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-modbustcp
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-motordrive.can0
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-motordrive.can1
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-mqtt
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-pump
drwxr-xr-x    4 root     root         100 May 24 19:36 dbus-qwacs
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-rv-c.can0
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-rv-c.can1
drwxr-xr-x    4 root     root         100 May 24 19:36 dbus-systemcalc-py
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-tempsensor-relay
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-valence.can0
drwxr-xr-x    4 root     root         120 May 24 19:36 dbus-valence.can1
drwxr-xr-x    4 root     root         100 May 24 19:36 dbus-vebus-to-pvinverter
drwxr-xr-x    4 root     root         100 May 24 19:36 gui
drwxr-xr-x    4 root     root         120 May 24 19:36 hostapd
drwxr-xr-x    4 root     root         100 May 24 19:36 hub4control
drwxr-xr-x    4 root     root         100 May 24 19:36 llmnrd
drwxr-xr-x    4 root     root         100 May 24 19:36 localsettings
drwxr-xr-x    4 root     root         120 May 24 19:36 mosquitto
drwxr-xr-x    4 root     root         120 May 24 19:36 mqtt-n2k.can0
drwxr-xr-x    4 root     root         120 May 24 19:36 mqtt-n2k.can1
drwxr-xr-x    4 root     root         120 May 24 19:36 mqtt-rpc
drwxr-xr-x    4 root     root         100 May 24 19:36 netmon
drwxr-xr-x    4 root     root         120 May 24 19:36 node-red-venus
drwxr-xr-x    4 root     root         120 May 24 19:36 openssh
drwxr-xr-x    4 root     root         120 May 24 19:36 ppp
drwxr-xr-x    4 root     root         100 May 24 19:36 serial-starter
drwxr-xr-x    4 root     root         100 May 24 19:36 service-advertiser
drwxr-xr-x    4 root     root         120 May 24 19:36 signalk-server
drwxr-xr-x    4 root     root         100 May 24 19:36 simple-upnpd
drwxr-xr-x    4 root     root         120 May 24 19:36 socketcand
drwxr-xr-x    4 root     root         120 May 24 19:36 ssh-tunnel
drwxr-xr-x    4 root     root         120 May 24 19:36 vecan-dbus.can0
drwxr-xr-x    4 root     root         120 May 24 19:36 vecan-dbus.can1
drwxr-xr-x    4 root     root         120 May 24 19:36 vegetty
drwxr-xr-x    4 root     root         100 May 24 19:36 venus-button-handler
drwxr-xr-x    4 root     root         100 May 24 19:36 venus-html5-logger
drwxr-xr-x    4 root     root         100 May 24 19:36 venus-platform
drwxr-xr-x    4 root     root         120 May 24 19:36 vesmart-server
drwxr-xr-x    4 root     root         100 May 24 19:36 vrmlogger
drwxr-xr-x    4 root     root         120 May 24 19:36 websockify-c
lrwxrwxrwx    1 root     root          37 May 24 19:37 mk2-dbus.ttyS4 -> /var/volatile/services/mk2-dbus.ttyS4
lrwxrwxrwx    1 root     root          47 May 24 19:37 vedirect-interface.ttyS5 -> /var/volatile/services/vedirect-interface.ttyS5
lrwxrwxrwx    1 root     root          47 May 24 19:37 vedirect-interface.ttyS6 -> /var/volatile/services/vedirect-interface.ttyS6
lrwxrwxrwx    1 root     root          47 May 24 19:37 vedirect-interface.ttyS7 -> /var/volatile/services/vedirect-interface.ttyS7

Now that I remember, I had some problem with that version with USB dbus manager that didn't unlock an USB dongle that I used on node-red when commanded to, and that was related to that this folder. After issuing the unlock cmd the usb device redirection was still there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@SergioRius @jsalbre @kwindrem