Quantcast
Viewing all articles
Browse latest Browse all 3254

Re: Lighttpd stopped working

Thank you.
Of course, I should've thought of that, although I'd removed the install folder after installation. Anyway, I reinstalled lighttpd:

root@2141530006545:~# opkg install -d ext /mnt/usb/install/cache/lighttpd*
Installing lighttpd-mod-alias (1.4.30-2) to ext...
Installing lighttpd (1.4.30-2) to ext...
Installing lighttpd-mod-cgi (1.4.30-2) to ext...
Installing lighttpd-mod-fastcgi (1.4.30-2) to ext...
Installing lighttpd-mod-redirect (1.4.30-2) to ext...
Installing lighttpd-mod-setenv (1.4.30-2) to ext...
Package lighttpd (1.4.30-2) installed in ext is up to date.
Configuring lighttpd.
Configuring lighttpd-mod-cgi.
Configuring lighttpd-mod-setenv.
Configuring lighttpd-mod-redirect.
Configuring lighttpd-mod-alias.
Configuring lighttpd-mod-fastcgi.


However, the problem persists:

root@2141530006545:~# dmesg | tail
[ 52.770000] Adding 32760k swap on /mnt/usb/external_fs/OpenWRT.swap. Priority:-1 extents:1 across:32760k
[ 340.960000] EXT4-fs (loop1): error count: 80
[ 340.960000] EXT4-fs (loop1): initial error at 76: mb_free_blocks:1348: block 17937
[ 340.970000] EXT4-fs (loop1): last error at 69: ext4_mb_generate_buddy:739
[ 478.100000] EXT4-fs error (device loop1): ext4_mb_generate_buddy:739: group 2, 3840 clusters in bitmap, 3846 in gd
[ 478.110000] JBD2: Spotted dirty metadata buffer (dev = loop1, blocknr = 1). There's a risk of filesystem corruption in case of system crash.


Again, the last two lines of the log were added after running piratebox.

The log states a problem with loop1 device, and the filesystem is mounted on loop0. So I think it is actually a problem with accessing some configuration file within pbIMG_ws.img. I will take a deeper look at that and report it.

Viewing all articles
Browse latest Browse all 3254

Trending Articles