NextcloudPi on a Rock64

ncp

#21

installation failed for some reason. Maybe to run it again on a clean armbian build and capture installation output / errors.

@Jeffery_Frederick has confirmed that this has to work :wink:


#22

I installed several times from scratch. The first time it worked perfectly, then I modified some values and i started from scratch again … since then I tried again to install four or five times :frowning:

@nachoparker here paste log of installation link


#23

did you start from flashing the armbian image?


#24

the log looks ok, but redis and apache are down. Can you give me

systemctl status apache2
systemctl status redis

and apache2 and redis logs?


#25

yep, I started flashing armbian image Armbian_5.42_Rock64_Debian_stretch_default_4.4.124_desktop.img


#26

ok, what about the logs then?


#27

here you have status of apache2 and redis

root@rock64:~# systemctl status apache2

● apache2.service - The Apache HTTP Server

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

Active: failed (Result: exit-code) since Sun 2018-04-22 18:13:39 UTC; 34min ago

Apr 22 18:13:38 rock64 systemd[1]: Starting The Apache HTTP Server…

Apr 22 18:13:39 rock64 apachectl[834]: (2)No such file or directory: AH02291: Cannot access directory ‘/var/log/apache2/’ for main e

Apr 22 18:13:39 rock64 apachectl[834]: AH00014: Configuration check failed

Apr 22 18:13:39 rock64 apachectl[834]: Action ‘start’ failed.

Apr 22 18:13:39 rock64 apachectl[834]: The Apache error log may have more information.

Apr 22 18:13:39 rock64 systemd[1]: apache2.service: Control process exited, code=exited status=1

Apr 22 18:13:39 rock64 systemd[1]: Failed to start The Apache HTTP Server.

Apr 22 18:13:39 rock64 systemd[1]: apache2.service: Unit entered failed state.

Apr 22 18:13:39 rock64 systemd[1]: apache2.service: Failed with result ‘exit-code’.

Apr 22 18:14:49 rock64 systemd[1]: apache2.service: Unit cannot be reloaded because it is inactive.

root@rock64:~#

root@rock64:~# systemctl status redis

● redis-server.service - Advanced key-value store

Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Sun 2018-04-22 18:13:40 UTC; 34min ago

Docs: http://redis.io/documentation,

man:redis-server(1)

Apr 22 18:13:40 rock64 systemd[1]: redis-server.service: Unit entered failed state.

Apr 22 18:13:40 rock64 systemd[1]: redis-server.service: Failed with result ‘exit-code’.

Apr 22 18:13:40 rock64 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.

Apr 22 18:13:40 rock64 systemd[1]: Stopped Advanced key-value store.

Apr 22 18:13:40 rock64 systemd[1]: redis-server.service: Start request repeated too quickly.

Apr 22 18:13:40 rock64 systemd[1]: Failed to start Advanced key-value store.

Apr 22 18:13:40 rock64 systemd[1]: redis-server.service: Unit entered failed state.

Apr 22 18:13:40 rock64 systemd[1]: redis-server.service: Failed with result ‘exit-code’.

Apr 22 18:20:14 rock64 systemd[1]: [/lib/systemd/system/redis-server.service:14] Unknown lvalue ‘RunTimeDirectory’ in section 'Servi

Apr 22 18:20:15 rock64 systemd[1]: [/lib/systemd/system/redis-server.service:14] Unknown lvalue ‘RunTimeDirectory’ in section 'Servi

root@rock64:~#

root@rock64:~#

now im looking for the path where logs apache and redis are stored :-/


#28

again, /var/log/apache2 doesn’t get created?? I don’t understand why apt doesn’t create it sometimes!

now the redis error is a new one


#29

what are the contents of /lib/systemd/system/redis-server.service


#30

I supposed that, but seems that into var/log there are not apache logs or redis

root@rock64:/var/log# ls -la
total 1960
drwxr-xr-x 5 root root 4096 Apr 22 18:13 .
drwxr-xr-x 13 root root 4096 Apr 22 16:43 …
-rw-r–r-- 1 root root 188 Apr 22 18:09 alternatives.log
drwxr-xr-x 2 root root 4096 Apr 22 18:08 apt
-rw-r–r-- 1 root root 145980 Apr 22 18:13 armhwinfo.log
-rw-r----- 1 root adm 23688 Apr 22 18:55 auth.log
-rw------- 1 root utmp 0 Apr 22 18:04 btmp
drwxr-x— 2 root lp 4096 Apr 22 18:04 cups
-rw-r----- 1 root adm 180527 Apr 22 18:56 daemon.log
-rw-r----- 1 root adm 34431 Apr 22 18:13 debug
-rw-r–r-- 1 root root 19920 Apr 22 18:09 dpkg.log
-rw-r–r-- 1 root root 1770 Apr 22 18:09 fontconfig.log
-rw-r----- 1 root adm 264611 Apr 22 18:56 kern.log
-rw-r----- 1 root adm 1557 Apr 22 18:40 mail.info
-rw-r----- 1 root adm 1557 Apr 22 18:40 mail.log
-rw-r----- 1 root adm 389527 Apr 22 18:56 messages
-rw-r----- 1 root www-data 8811 Apr 22 18:21 ncp.log
-rw------- 1 root root 748 Apr 22 18:13 php7.0-fpm.log
-rw-r----- 1 root adm 640975 Apr 22 18:56 syslog
drwxr-xr-x 2 root root 4096 Apr 22 18:40 unattended-upgrades
-rw-r----- 1 root adm 191032 Apr 22 18:56 user.log
-rw-rw-r-- 1 root utmp 7200 Apr 22 18:14 wtmp
-rw-r–r-- 1 root root 9529 Apr 22 18:13 Xorg.0.log
-rw-r–r-- 1 root root 9529 Apr 22 18:13 Xorg.0.log.old


#31

if you look at this issue you can just create them, but I just can’t understand why they don’t get created :S


#32

here contents of /lib…/…/redis-server.service

root@rock64:/var/log# cat /lib/systemd/system/redis-server.service


root@rock64:/var/log# cat /lib/systemd/system/redis-server.service

[Unit]

Description=Advanced key-value store

After=network.target

Documentation=http://redis.io/documentation, man:redis-server(1)

[Service]

Type=forking

ExecStart=/usr/bin/redis-server /etc/redis/redis.conf

PIDFile=/var/run/redis/redis-server.pid

TimeoutStopSec=0

Restart=always

User=redis

Group=redis

RunTimeDirectory=redis

ExecStartPre=-/bin/run-parts --verbose /etc/redis/redis-server.pre-up.d

ExecStartPost=-/bin/run-parts --verbose /etc/redis/redis-server.post-up.d

ExecStop=-/bin/run-parts --verbose /etc/redis/redis-server.pre-down.d

ExecStop=/bin/kill -s TERM $MAINPID

ExecStopPost=-/bin/run-parts --verbose /etc/redis/redis-server.post-down.d

UMask=007

PrivateTmp=yes

LimitNOFILE=65535

PrivateDevices=yes

ProtectHome=yes

ReadOnlyDirectories=/

ReadWriteDirectories=-/var/lib/redis

ReadWriteDirectories=-/var/log/redis

ReadWriteDirectories=-/var/run/redis

CapabilityBoundingSet=~CAP_SYS_PTRACE

# redis-server writes its own config file when in cluster mode so we allow

# writing there (NB. ProtectSystem=true over ProtectSystem=full)

ProtectSystem=true

ReadWriteDirectories=-/etc/redis

[Install]

WantedBy=multi-user.target

Alias=redis.service

#33

I am now suspecting this is something related to a problem with logs2ram …

If you create the directories and give them permissions, everything should work. I will reopen the issue and we can continue there :wink:

Thanks for your help!


#34

this is exactly what i did one of the times… :stuck_out_tongue:
i will follow the issues in order to help with this, ok!


#35

great, thanks!


#36

I think that the issue is fixed. Please, follow up on github to verify :wink:


#37

Just FYI I had the /var/log/apache2 issue also. I reinstalled Armbian from scratch and then installed Apache BEFORE I installed NextcloudPlus. All worked well at that point.


#38

Hi!

i have installed from scratch OS and followed procedure to install ncp. Until now seems the installation has finished successfully and seems that is working everything fine, I’m going to test now some addons and will come with news later.


#39

great! finally found where the issue was and it is now solved :slight_smile:

now it seems that we need to wait for armbian to finish their work on the rock64


#40

since yesterday I am testing new release of ncp plus and until now everything is perfect!
i have very good feeling running this release with HW rock64