App Central ends support for KODI (what we can do)
- father.mande
- Posts: 1817
- youtube meble na wymiar Warszawa
- Joined: Sat Sep 12, 2015 2:55 am
- Location: La Rochelle (France)
Re: App Central ends support for KODI (what we can do)
Hi,
Please after doing : myHD start (or now if you don't change from last test)
do : tmux a
... then copy here the content of the screen (do exit to quit tmux)
myHD is started in a tmux windows (tmux is an alternative to screen)
Philippe.
NB please confirm your model and A.D.M. version
Please after doing : myHD start (or now if you don't change from last test)
do : tmux a
... then copy here the content of the screen (do exit to quit tmux)
myHD is started in a tmux windows (tmux is an alternative to screen)
Philippe.
NB please confirm your model and A.D.M. version
Last edited by father.mande on Wed Jul 24, 2019 1:31 pm, edited 1 time in total.
AS6602T / AS5202T /AS5002T / AS1002T / FS6706T
-
- Posts: 36
- Joined: Wed Jul 17, 2019 9:01 pm
Re: App Central ends support for KODI (what we can do)
tmux -a doesn't work:
ADM version 3.4.0R5E3
NAS type AS5202T
CPU Celeron J4005
8 GB memory
Dirk
Code: Select all
root@AS5202T-1187:/ # myHD start
myHD start ... requested
get keys from Asportal / get sound def.
myHD astr user exist ...
Download Ubuntu if not yet available
Now start jchroot in background
now start in background a survey to manage a clean exit
==== PROBLEM : dropbear is not started after 1 minutes
==== DO NOTHING more
root@AS5202T-1187:/ # tmux -a
tmux: unknown option -- a
usage: tmux [-2CluvV] [-c shell-command] [-f file] [-L socket-name]
[-S socket-path] [command [flags]]
ADM version 3.4.0R5E3
NAS type AS5202T
CPU Celeron J4005
8 GB memory
Dirk
- father.mande
- Posts: 1817
- Joined: Sat Sep 12, 2015 2:55 am
- Location: La Rochelle (France)
Re: App Central ends support for KODI (what we can do)
Hi,
OUPSSS!
it's : tmux a (without hyphen) ... corrected in my previous post now
so sorry
Philippe.
NB if possible (depend of your activity) you can try also to reboot, because something goes wrong without a clear explain ...
NB 2 in the future, open a separate topic for problems, more easy to manage (and in myHD sub-forum ... if possible)
OUPSSS!
it's : tmux a (without hyphen) ... corrected in my previous post now
so sorry
Philippe.
NB if possible (depend of your activity) you can try also to reboot, because something goes wrong without a clear explain ...
NB 2 in the future, open a separate topic for problems, more easy to manage (and in myHD sub-forum ... if possible)
AS6602T / AS5202T /AS5002T / AS1002T / FS6706T
-
- Posts: 36
- Joined: Wed Jul 17, 2019 9:01 pm
Re: App Central ends support for KODI (what we can do)
This is a kind of crash course in Linux for me
Anyway, I don't understand what is going on:
The myHD share is clearly present ?!?
Anyway, I don't understand what is going on:
Code: Select all
login as: root
Keyboard-interactive authentication prompts from server:
| Password:
End of keyboard-interactive prompts from server
root@AS5202T-1187:/volume1/.@root # myHD start
myHD start ... requested
get keys from Asportal / get sound def.
myHD astr user exist ...
Download Ubuntu if not yet available
Now start jchroot in background
now start in background a survey to manage a clean exit
==== PROBLEM : dropbear is not started after 1 minutes
==== DO NOTHING more
root@AS5202T-1187:/volume1/.@root # tmux a
/usr/local/AppCentral/myHD/bin/jchroot -p /tmp/myHD.pid -u 0 -g 0 -f /usr/local/AppCentral/myHD/fstab_myHD /usr/local/.myHD/1804 -- /bin/bash
root@AS5202T-1187:/volume1/.@root # /usr/local/AppCentral/myHD/bin/jchroot -p /
tmp/myHD.pid -u 0 -g 0 -f /usr/local/AppCentral/myHD/fstab_myHD /usr/local/.myHD
/1804 -- /bin/bash
unable to mount '/share/myHD' on 'permanent': No such file or directory
root@AS5202T-1187:/volume1/.@root # /myHD_scripts/bin/rcS
-sh: /myHD_scripts/bin/rcS: not found
root@AS5202T-1187:/volume1/.@root # /myHD_scripts/bin/rc.local start
-sh: /myHD_scripts/bin/rc.local: not found
root@AS5202T-1187:/volume1/.@root #
root@AS5202T-1187:/volume1 # ls
Picture/ Plex/ Projecten/ Public/ Video/ Web/ home/ myHD/
root@AS5202T-1187:/volume1 #
- father.mande
- Posts: 1817
- Joined: Sat Sep 12, 2015 2:55 am
- Location: La Rochelle (France)
Re: App Central ends support for KODI (what we can do)
Hi,
No, it's because you don't have a /share/myHD in /share or at minimal no access right for it ???
verify doing : ls -ali /share
and do (to verify syntax) :
cat /usr/local/AppCentral/myHD/fstab_include
Please try first without this shared resource, so please try first :
1) stop myHD : myHD stop
2) go to folder /usr/local/AppCentral/myHD
cd /usr/local/AppCentral/myHD
3) delete file fstab_include and recreate it empty
rm -f fstab_include
touch fstab_include
4) restart myHD : myHD start
... if all start as expected ... go to myHD WebUI and add resource (ONLY valid (existing) resources in /share are listed and available for added it ... ) ; then restart myHD (command or WebUI to activate it)
Philippe.
No, it's because you don't have a /share/myHD in /share or at minimal no access right for it ???
(I will add a check in next version to avoid this problem ... )unable to mount '/share/myHD' on 'permanent': No such file or directory
verify doing : ls -ali /share
and do (to verify syntax) :
cat /usr/local/AppCentral/myHD/fstab_include
Please try first without this shared resource, so please try first :
1) stop myHD : myHD stop
2) go to folder /usr/local/AppCentral/myHD
cd /usr/local/AppCentral/myHD
3) delete file fstab_include and recreate it empty
rm -f fstab_include
touch fstab_include
4) restart myHD : myHD start
... if all start as expected ... go to myHD WebUI and add resource (ONLY valid (existing) resources in /share are listed and available for added it ... ) ; then restart myHD (command or WebUI to activate it)
Philippe.
AS6602T / AS5202T /AS5002T / AS1002T / FS6706T
-
- Posts: 36
- Joined: Wed Jul 17, 2019 9:01 pm
Re: App Central ends support for KODI (what we can do)
hi,
The problem is that the /share/myHD directory does exist!
The myHD WebUI will not start, it only causes a short 'blink' on the screen.
The problem is that the /share/myHD directory does exist!
Code: Select all
login as: root
Keyboard-interactive authentication prompts from server:
| Password:
End of keyboard-interactive prompts from server
root@AS5202T-1187:/volume1/.@root # ls -ali /share
total 34
2 drwxr-xr-x 11 root root 1024 Jul 24 15:25 ./
2 drwxr-xr-x 21 root root 600 Jul 23 11:56 ../
21603 drwxrwxrwx 1 admin administ 22 Jul 23 12:01 Picture/
3386 drwxrwxrwx 1 admin administ 14 Jul 21 17:24 Plex/
21686 drwxrwxrwx 1 admin administ 64 Jul 23 12:34 Projecten/
265 drwxrwxrwx 1 admin administ 266 Jul 23 01:24 Public/
1 drwxrwxrwx 3 admin administ 32768 Jan 1 1970 USB1/
2235 drwxrwxrwx 1 admin administ 22 Jul 21 13:18 Video/
274 drwxrwxrwx 1 admin administ 130 Jul 22 21:58 Web/
263 drwxr-xr-x 1 root root 18 Jul 22 21:58 home/
17 drwx------ 2 root root 1024 Jul 24 15:25 myHD/
root@AS5202T-1187:/volume1/.@root # cat /usr/local/AppCentral/myHD/fstab_include
/share/myHD:permanent
root@AS5202T-1187:/volume1/.@root # myHD status
==== is myHD running ?
==== myHD is NOT running
====
root@AS5202T-1187:/volume1/.@root # cd /usr/local/AppCentral/myHD
root@AS5202T-1187:/volume1/.@plugins/AppCentral/myHD # ls
CONTROL/ fstab_myHD myHD_1604.conf myHD_apkg/
bin/ fstab_temp myHD_1604_home_delivery.tgz myHD_external.conf
fake_apkg/ modules/ myHD_1804.conf myHD_temp/
files/ myHD.conf myHD_1804_home_delivery.tgz scripts/
fstab_include myHD.sh* myHD_App.conf www@
root@AS5202T-1187:/volume1/.@plugins/AppCentral/myHD # rm fstab_include
root@AS5202T-1187:/volume1/.@plugins/AppCentral/myHD # touch fstab_include
root@AS5202T-1187:/volume1/.@plugins/AppCentral/myHD # myHD start
myHD start ... requested
get keys from Asportal / get sound def.
myHD astr user exist ...
Download Ubuntu if not yet available
Now start jchroot in background
now start in background a survey to manage a clean exit
time to do extra works in myHD
set keys and files for user admin
set keys and files for user astr
create or verify authorized_keys for ADM root user
keys for myHD root user is already installed
Background interface to solve some launch problems (like AppImage)
Start background interface for user admin
Start background interface for user astr
Init alsa
root@AS5202T-1187:/volume1/.@plugins/AppCentral/myHD # myHD status
==== is myHD running ?
==== myHD is running
==== myHD Version 0.9.4
====
==== Ubuntu Version in use : 1804
====
==== PID is 24612
====
==== List of tasks running in myHD
==== ==== PID are internal to myHD not as in A.D.M.
==== ==== user name are internal to myHD not as in A.D.M.
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 15:48 ? 00:00:00 /bin/bash
root 71 1 0 15:48 ? 00:00:00 /usr/sbin/cron
message+ 91 1 0 15:48 ? 00:00:00 /usr/bin/dbus-daemon --system
root 98 1 0 15:48 ? 00:00:00 /usr/sbin/dropbear -p 6222 -W 65536
admin 153 1 0 15:48 ? 00:00:00 /bin/bash /myHD_scripts/bin/myserv_user
astr 169 1 0 15:48 ? 00:00:00 /bin/bash /myHD_scripts/bin/myserv_user
root 176 1 0 15:49 ? 00:00:00 ps -eaf
====
==== List of user know by myHD
LIST of user in myHD :
root (NOT Asustor root user but real root myHD user)
admin
astr (it's Asustor root user MAPPED as astr user in myHD)
End of the list
====
==== port used by myHD internal dropbear server
Internal Listen interface and port used :
DROPBEAR_PORT=6222
====
==== List shared ressources defined in myHD
====
root@AS5202T-1187:/volume1/.@plugins/AppCentral/myHD #
- father.mande
- Posts: 1817
- Joined: Sat Sep 12, 2015 2:55 am
- Location: La Rochelle (France)
Re: App Central ends support for KODI (what we can do)
Hi,
Yes, myHD exist BUT who add permanent after /share/myHD: in fstab_include ??? it's NOT the correct format
... be attention to don't restrict /share/myHD to root only (as now in your system) because Kodi or other applications are started under astr user ... so can't have access to it.
Please just keep /share/myHD: in fstab_include don't add anything after ...
better after restarting well (as you trace said) use myHD command to add /share/myHD
myHD add_include_folder /share/myHD (seems comment in myHD Usage can generate a misunderstanding, I will correct it in next release. )
then restart myHD
for the WebUI it's because you don't enable the Web server in A.D.M. (services / web server), I can't for security decide myself to enable the web server (reason to have all, also in command line)
after enabling it, restart myHD (soory but it's need to add a secure access user / password (myhd / asusfr1)
Philippe.
NB myHD shared resource is an option, if you prefer share Music and Media and don't add a specific share for myHD
Yes, myHD exist BUT who add permanent after /share/myHD: in fstab_include ??? it's NOT the correct format
... be attention to don't restrict /share/myHD to root only (as now in your system) because Kodi or other applications are started under astr user ... so can't have access to it.
Please just keep /share/myHD: in fstab_include don't add anything after ...
better after restarting well (as you trace said) use myHD command to add /share/myHD
myHD add_include_folder /share/myHD (seems comment in myHD Usage can generate a misunderstanding, I will correct it in next release. )
then restart myHD
for the WebUI it's because you don't enable the Web server in A.D.M. (services / web server), I can't for security decide myself to enable the web server (reason to have all, also in command line)
after enabling it, restart myHD (soory but it's need to add a secure access user / password (myhd / asusfr1)
Philippe.
NB myHD shared resource is an option, if you prefer share Music and Media and don't add a specific share for myHD
AS6602T / AS5202T /AS5002T / AS1002T / FS6706T
-
- Posts: 36
- Joined: Wed Jul 17, 2019 9:01 pm
Re: App Central ends support for KODI (what we can do)
I added permanent, assuming this means that myHD always has to use this share, not just this one time.
Indeed i had not set up the webserver, saw no need for it just now. But your application needs its, so I will enable it.
Don't know when I can try it out now, since after an update to 3.4.0R7N3 I have no picture on my TV, except for the mouse cursor. AiRemote does not work either, it can not see the NAS.Tony from Asustor support will be happy with my ticket.
Question: can you also make the Videolan VLC player work with myHD? They have an Ubuntu version. That would be great, I've used it on my PC for years now.
Indeed i had not set up the webserver, saw no need for it just now. But your application needs its, so I will enable it.
Don't know when I can try it out now, since after an update to 3.4.0R7N3 I have no picture on my TV, except for the mouse cursor. AiRemote does not work either, it can not see the NAS.Tony from Asustor support will be happy with my ticket.
Question: can you also make the Videolan VLC player work with myHD? They have an Ubuntu version. That would be great, I've used it on my PC for years now.
- father.mande
- Posts: 1817
- Joined: Sat Sep 12, 2015 2:55 am
- Location: La Rochelle (France)
Re: App Central ends support for KODI (what we can do)
Hi,
2) vlc ... yes why not it's not a problem
Philippe.
1) I have same problem with 3.4.0.R7N3 ... n my system I just enable Asportal, then all applications ... seems Update disabled it (I have write a post on this)Caesar-NL wrote:I added permanent, assuming this means that myHD always has to use this share, not just this one time.
Indeed i had not set up the webserver, saw no need for it just now. But your application needs its, so I will enable it.
Don't know when I can try it out now, since after an update to 3.4.0R7N3 I have no picture on my TV, except for the mouse cursor. AiRemote does not work either, it can not see the NAS.Tony from Asustor support will be happy with my ticket.
Question: can you also make the Videolan VLC player work with myHD? They have an Ubuntu version. That would be great, I've used it on my PC for years now.
2) vlc ... yes why not it's not a problem
Philippe.
AS6602T / AS5202T /AS5002T / AS1002T / FS6706T
-
- Posts: 36
- Joined: Wed Jul 17, 2019 9:01 pm
Re: App Central ends support for KODI (what we can do)
Hi Philippe,
Everything is working now, hurray !!!
In case your NAS has got a black screen on the TV after the ADM update as well, do this:
By the way, Kodi 18.3 is current.
Everything is working now, hurray !!!
In case your NAS has got a black screen on the TV after the ADM update as well, do this:
- Switch off your TV
- remove Asustor Portal from the NAS (with AppCentral)
- Restart the NAS
- Install Asustor Portal again
- shut down the NAS
- Switch on the TV
- Start the NAS
By the way, Kodi 18.3 is current.