LINUX.ORG.RU
решено ФорумAdmin

synology не отображает web морду

 


0

1

Здравствуйте. После того как на разделе /dev/root закончилось место synology перестала отображать web морду авторизации, вместо неё тупо белый экран, очистка места проблему не решила, подскажите куда копать?

https://ibb.co/ZxgSKtp

После того как на разделе /dev/root закончилось место

м?
мм?
ему развернуться негде, как он демон стартанёт, если места нет?

darkenshvein ★★★★★ ()
Ответ на: комментарий от darkenshvein
Filesystem         Size  Used Avail Use% Mounted on
/dev/root          2.3G  2.0G  254M  89% /
/tmp               1.8G  268K  1.8G   1% /tmp
/run               1.8G  4.0M  1.8G   1% /run
/dev/shm           1.8G     0  1.8G   0% /dev/shm
none               4.0K     0  4.0K   0% /sys/fs/cgroup
/dev/bus/usb       1.8G  4.0K  1.8G   1% /proc/bus/usb
/dev/vg1/volume_2  218G  101G  117G  47% /volume2
/volume1/@optware  3.4T  1.6T  1.8T  47% /opt
/dev/sdu1           24M   18M  6.9M  72% /volumeUSB1/usbshare

11% процентов должно хватать

depresnak ()
Ответ на: комментарий от darkenshvein

А можно конкретней логи чего?

вот например логи файлов за последние 2 дня и есть наверное ещё куча логов без .log

server4> find /root/-name *.log -type f -mtime +2
find: /root/-name: No such file or directory
find: *.log: No such file or directory
server4> find /root/ -name *.log -type f -mtime +2
server4> find / -name *.log -type f -mtime +2
/volume2/@appstore/mc/var/mc_install.log
/volume2/@appstore/nano/var/nano_install.log
/volume2/@appstore/Tomcat7/src/logs/catalina.2018-12-20.log
/volume2/@appstore/Tomcat7/src/logs/localhost.2018-12-20.log
/volume2/@appstore/Tomcat7/src/logs/manager.2018-12-20.log
/volume2/@appstore/Tomcat7/src/logs/host-manager.2018-12-20.log
/volume2/@appstore/Odoo8/log/server.log
/volume2/owncloud/owncloud.log
/volume2/@docker/aufs/diff/c1f98057d627496e1843020c45c444f7572b581ef440e7c177f3a4834d483609/var/log/alternatives.lo                   g
/volume2/@docker/aufs/diff/c1f98057d627496e1843020c45c444f7572b581ef440e7c177f3a4834d483609/var/log/apt/history.log
/volume2/@docker/aufs/diff/c1f98057d627496e1843020c45c444f7572b581ef440e7c177f3a4834d483609/var/log/apt/term.log
/volume2/@docker/aufs/diff/c1f98057d627496e1843020c45c444f7572b581ef440e7c177f3a4834d483609/var/log/bootstrap.log
/volume2/@docker/aufs/diff/c1f98057d627496e1843020c45c444f7572b581ef440e7c177f3a4834d483609/var/log/dpkg.log
/volume2/@docker/aufs/diff/ebafc223afc8b7ce8a2a7a0337a11eac9b3b5fb5d6736f762d68757102a0b906/var/log/apt/history.log
/volume2/@docker/aufs/diff/ebafc223afc8b7ce8a2a7a0337a11eac9b3b5fb5d6736f762d68757102a0b906/var/log/apt/term.log
/volume2/@docker/aufs/diff/ebafc223afc8b7ce8a2a7a0337a11eac9b3b5fb5d6736f762d68757102a0b906/var/log/dpkg.log
/volume2/@docker/aufs/diff/52194afe9078e5500fbd2cc45ba726d3b47b099207675c4c0779e143f9dc8cdf/supervisord.log
/volume2/@docker/aufs/diff/52194afe9078e5500fbd2cc45ba726d3b47b099207675c4c0779e143f9dc8cdf/tmp/netxms-nxagent-stdo                   ut---supervisor-xou90_.log
/volume2/@docker/aufs/diff/52194afe9078e5500fbd2cc45ba726d3b47b099207675c4c0779e143f9dc8cdf/tmp/netxms-nxagent-stde                   rr---supervisor-fwwu78.log
/volume2/@docker/aufs/diff/52194afe9078e5500fbd2cc45ba726d3b47b099207675c4c0779e143f9dc8cdf/tmp/netxms-server-stdou                   t---supervisor-6GUBIx.log
/volume2/@docker/aufs/diff/52194afe9078e5500fbd2cc45ba726d3b47b099207675c4c0779e143f9dc8cdf/tmp/netxms-server-stder                   r---supervisor-0UfhW3.log
/volume2/@docker/vfs/dir/2ef808dd2b4080ac9d8eb13c375a4588899f812f48d827023134fee1a7c15b7e/netxms.log
/volume2/@docker/vfs/dir/1662d82fdcf80a11bf7ffee235174cc0e004c6ab47d528a925fa1aa84755a941/netxms.log
/opt/zabbix/agentd.log
/var/log/upstart/update-apppriv-local.log
/var/log/upstart/update-apppriv-remote.log
/var/log/upstart/dhcp-client-eth0.log
/var/log/upstart/minissdpd.log
/var/log/upstart/synosnmpcd.log
/var/log/upstart/netatalk.log
/var/log/upstart/DiskHealthCk.log
/var/log/upstart/pppoerelay.log
/var/log/upstart/smallupdate.log
/var/log/upstart/gcpd.log
/var/log/upstart/synolog-service-handler-ftpd.log
/var/log/upstart/synolog-service-handler-ftpd-ssl.log
/var/log/upstart/ftpd.log
/var/log/upstart/webstation-httpd-conf-writer.log
/var/log/upstart/ssh-sftp.log
/var/log/upstart/synolog-service-handler-sftp.log
/var/log/synolog/synoindex.log
/var/log/synolog/synodockerwebapi.log
/var/log/synorelayd.log
/var/log/synoupdate.log
/var/log/dpkg_upgrade.log
/var/log/dpkg.log
/var/log/mount.log
/var/log/Docker/docker.log
/var/log/Docker/termd.log
/volume1/Backup/#recycle/Training/GEOS-K11/Logs/Backup_Error-04-02-2019_10-08-27.log
/volume1/web/owncloud/data/owncloud.log
/volume1/@optware/zabbix/agentd.log

depresnak ()
Ответ на: комментарий от darkenshvein

/var/log/synolog/synoindex.log

Apr 24 15:30:34 server4 synomkthumbd: synoidx_ipc_core.cpp:111 [Error] connect server: /tmp/synoindexplugind_sock
Apr 24 15:30:34 server4 synomkthumbd: synomk_ipc.cpp:110 fail
Apr 24 15:30:34 server4 synomkflvd: synoidx_ipc_core.cpp:111 [Error] connect server: /tmp/synoindexplugind_sock
Apr 24 15:30:34 server4 synomkflvd: synomk_ipc.cpp:83 fail

/var/log/synolog/synodockerwebapi.log

netxms-server - мертворожденная идея

info    2019/01/18 09:23:24     samarapbadmin:  Stop container web.
info    2019/01/18 09:23:41     samarapbadmin:  Start container web.
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:latest
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:18     samarapbadmin:  Delete image lomo/netxms-webui:
info    2019/01/18 10:37:28     samarapbadmin:  Stop container web.
info    2019/01/18 10:37:34     samarapbadmin:  Stop container web.
info    2019/01/18 13:43:47     samarapbadmin:  Stop container netxms-server.
err     2019/01/18 13:44:26     samarapbadmin:  Start container netxms-server failed: Cannot start container 52194afe9078e5500fbd2cc45ba726d3b47b099207675c4c0779e143f9dc8c
df: Container is marked for removal and cannot be started.

/var/log/synorelayd.log

Apr 24 11:53:59 2018 synorelayd.cpp:1815 daemon started
Apr 24 11:53:59 2018 config.cpp:838 invalid mac address
Apr 24 11:54:19 2018 synorelayd.cpp:1859 daemon stopped

/var/log/synoupdate.log

2019/01/09 08:37:14     start critical update to buildnumber: 5967 original smallfixnumbre: 8 new_smallfixnumber: 9 build date: 2018/12/26
2019/01/09 08:37:15     Finished update before reboot!
2019/01/09 08:38:06     Finished critical update!!!

/var/log/kern.log

Feb 26 14:41:47 server4 kernel: [73508.434069] type=1400 audit(1551177707.013:47): apparmor="DENIED" operation="mkdir" parent=14492 profile="/usr/syno/synoman/webman/index
.cgi" name="/usr/syno/synoman/synohdpack/tmp/" pid=14526 comm="mkdir" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
depresnak ()
Ответ на: комментарий от darkenshvein

netxms-server

это ещё в январе было

меня больше вот это беспокоит:

apparmor=«DENIED» operation=«mkdir» причем сначала пытается создать, потом удалить

Feb 26 14:41:47 server4 kernel: [73508.434069] type=1400 audit(1551177707.013:47): apparmor="DENIED" operation="mkdir" parent=14492 profile="/usr/syno/synoman/webman/index
.cgi" name="/usr/syno/synoman/synohdpack/tmp/" pid=14526 comm="mkdir" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
Feb 26 15:11:24 server4 kernel: [75286.348943] type=1400 audit(1551179484.282:48): apparmor="DENIED" operation="rmdir" parent=15206 profile="/usr/syno/synoman/webman/index
.cgi" name="/usr/syno/synoman/synohdpack/tmp/" pid=15268 comm="rm" requested_mask="d" denied_mask="d" fsuid=0 ouid=0

depresnak ()
Ответ на: комментарий от darkenshvein

/usr/syno/synoman/synohdpack/tmp/ или /tmp/synoindexplugind_sock если в /tmp то после каждого ребута он их создает автоматом, если в /usr/syno/synoman/synohdpack/tmp/, то папки такой вообще нет(создание вручную ни к чему не приводит)

depresnak ()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.