Version 1.11.0 : Based on OpenWrt 18.06

The latest news about Gargoyle

Moderator: Moderators

RomanHK
Posts: 667
Joined: Sat May 04, 2013 4:18 pm
Location: Czech Republik

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by RomanHK »

snake218 wrote:1. Didn't preserve settings, no backup used.
2. Wifi signal is ok, but connection to the internet drops
3. Didn't touch that setting

my problem could be memory related? I recently upgrade my internet connection from 10mb to 30mb, a lot of clients connect simultaneously to my network(around 15-20 max 30 clients). The problem is not with the wifi signal, but the connection. Downgrade to 1.10.0 and experience same issue once. The only solution is reboot the router. The problem maybe related to 30mb connection like i said before. Any advice? Do i change connection limits setting?

It would be good to write a log listing, please you can via ssh: logread
You can also find out the memory status via the ssh command: free
Provide this information just after an internet outage.

Concerning point 3, I am wondering if you have reached the max.
Turris Omnia with Gargoyle 1.12.0
Linksys WRT3200ACM with Gargoyle 1.12.0
TL-WR1043ND v2 with Gargoyle 1.10.0

Daeron
Posts: 28
Joined: Mon Oct 31, 2016 5:30 am

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by Daeron »

TL-WR1043ND v1.x (32MB RAM, 8MB flash, 400mhz CPU) running Gargoyle 1.11.0. Upgraded without attempting to preserve any previous settings.

I have noticed multiple problems compared to 1.09 and 1.10, both which ran very stable.

Attempting to access the Port Forwarding page results in either:
1) not loading at all (the background of the page is visible, but no interactive elements load)
2) loading after a significant delay (30 seconds or minutes)
3) loading normally (1-15 seconds)

Most of the other pages load in under 1-5 seconds.

The Plugins page can exhibit similar problems, but most importantly attempting to install plugins generally fails. After pressing the install button the page refreshes, the background is drawn but no UI elements are visible. Usually after 30 seconds or so the page refreshes again, now with the usual UI elements visible, but the plugin is not installed. After *many* tries like this, eventually the installation can succeed.

Under heavy load the router sometimes dies (web GUI becomes unavailable, DNS issues crop up, wifi and wired connections drop completely as if the router lost power). In around a minute the router may or may not recover on its own, or a power cycle will bring it back to functional state. Overall this happens fairly rarely, but enough to not be considered stable.

I also had some problems during the initial setup, saving various pages may lead to similar half-loaded state on the web GUI (usually for around a minute or a half), followed by either the settings successfully saved or the router dying. This also means I had to factory reset and start the initial configuration at least 1 or 2 times.

Attempting to change settings during any traffic (even less than 5mbps) can render the GUI significantly slower to load. This is especially true for saving QoS related settings and under full load (this is on a 30mbps connection) this can be painfully slow.

The load averages in the main status page can also shoot up to 2.5-3.5 territory seemingly without a reason (although most likely related to the slow loading or me checking the various pages/saving settings). Normally the router would stay well below 1.0 averages even under full load. Killing the traffic usually lets the router recover fairly quickly.

Note that I am using the Adblock plugin and 1 or 2 QoS classes based on packet lengths. This however was the case in the previous versions too.

I captured some logs which to me seems to suggest that the device is running out of memory?

When trying to access the Port Forwarding page:

Code: Select all

Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.485713] hostapd invoked oom-killer: gfp_mask=0x2420848(GFP_NOFS|__GFP_NOFAIL|__GFP_HARDWALL|__GFP_MOVABLE), nodemask=0, order=0, oom_score_adj=0
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.499601] CPU: 0 PID: 3866 Comm: hostapd Not tainted 4.9.156 #0
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.505946] Stack : 804c76c2 00000035 00000000 00000001 81998d04 80455267 804096c8 00000f1a
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.514475]         804c3800 8139bb58 00000001 00200000 00000000 800a96bc 00000000 00000004
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.523442]         00000006 80476624 8040d16c 8139b9d4 00000000 800d786c 804c76c2 00000088
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.532151]         00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.540653]         00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.549740]         ...
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.552217] Call Trace:
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.554694] [<8006b220>] show_stack+0x70/0x8c
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.559372] [<801185ac>] dump_header.isra.5+0x6c/0x160
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.564572] [<800dd338>] oom_kill_process+0xa8/0x438
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.570078] [<800ddc10>] out_of_memory+0x3c4/0x3e8
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.574936] [<800e1314>] __alloc_pages_nodemask+0x924/0x9ac
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.580584] [<800d97b4>] pagecache_get_page+0x268/0x34c
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.586115] [<8014b63c>] __getblk_gfp+0xfc/0x378
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.590839] [<80179f48>] squashfs_read_data+0x268/0x700
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.596695] [<8017e0c4>] squashfs_readpage_block+0x354/0x530
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.602459] [<8017be18>] squashfs_readpage+0x610/0x688
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.607849] [<800dbf74>] filemap_fault+0x444/0x5c4
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.612731] [<800fc788>] __do_fault+0x174/0x230
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.617300] [<800ffec8>] handle_mm_fault+0x448/0xb2c
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.622652] [<8007155c>] __do_page_fault+0x23c/0x468
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.627665] [<80065f80>] ret_from_exception+0x0/0x10
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.633213] Mem-Info:
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.635544] active_anon:1519 inactive_anon:40 isolated_anon:0
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.635544]  active_file:154 inactive_file:203 isolated_file:0
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.635544]  unevictable:0 dirty:0 writeback:0 unstable:0
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.635544]  slab_reclaimable:177 slab_unreclaimable:1541
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.635544]  mapped:14 shmem:174 pagetables:76 bounce:0
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.635544]  free:247 free_pcp:0 free_cma:0
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.668174] Node 0 active_anon:6076kB inactive_anon:160kB active_file:616kB inactive_file:812kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:56kB dirty:0kB writeback:0kB shmem:696kB writeback_tmp:0kB unstable:0kB pages_scanned:0 all_unreclaimable? yes
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.693126] Normal free:984kB min:1024kB low:1280kB high:1536kB active_anon:6076kB inactive_anon:160kB active_file:616kB inactive_file:812kB unevictable:0kB writepending:0kB present:32768kB managed:27636kB mlocked:0kB slab_reclaimable:708kB slab_unreclaimable:6164kB kernel_stack:392kB pagetables:304kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Sun Mar 24 09:50:28 2019 kern.emerg kernel: lowmem_reserve[]: 0 0
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.728582] Normal: 34*4kB (UM) 99*8kB (U) 4*16kB (U) 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 992kB
Sun Mar 24 09:50:28 2019 kern.emerg kernel: 531 total pagecache pages
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.743067] 0 pages in swap cache
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.746407] Swap cache stats: add 0, delete 0, find 0/0
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.752179] Free swap  = 0kB
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.755080] Total swap = 0kB
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.757975] 8192 pages RAM
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.761064] 0 pages HighMem/MovableOnly
Sun Mar 24 09:50:28 2019 kern.warn kernel: [ 1781.764924] 1283 pages reserved
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.768082] [ pid ]   uid  tgid total_vm      rss nr_ptes nr_pmds swapents oom_score_adj name
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.777194] [  481]     0   481      296       15       3       0        0             0 ubusd
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.785918] [  489]     0   489      225       10       3       0        0             0 askfirst
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.795616] [ 1112]     0  1112      310       34       4       0        0             0 logd
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.804579] [ 1185]     0  1185      266       10       3       0        0             0 dropbear
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.813826] [ 1265] 65534  1265      290       16       3       0        0             0 portmap
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.822711] [ 1293]     0  1293      430       42       4       0        0             0 netifd
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.831976] [ 1446]     0  1446      302       10       3       0        0             0 udhcpc
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.840990] [ 1477]     0  1477      303       17       4       0        0             0 ntpd
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.849620] [ 1692]     0  1692      798       55       5       0        0             0 uhttpd
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.858755] [ 2373]     0  2373      303       11       3       0        0             0 crond
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.867603] [ 3339]   453  3339      642      337       4       0        0             0 dnsmasq
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.876910] [ 3598]     0  3598      283       31       3       0        0             0 dropbear
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.885902] [ 3607]     0  3607      302       10       3       0        0             0 ash
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.894827] [ 3866]     0  3866      498       31       4       0        0             0 hostapd
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.903924] [ 4026]     0  4026      302       11       3       0        0             0 sh
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.912366] [ 4031]     0  4031      302       10       3       0        0             0 sh
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.921177] [ 4032]     0  4032     1446      732       4       0        0             0 opkg
Sun Mar 24 09:50:28 2019 kern.info kernel: [ 1781.930022] [ 4033]     0  4033      302       11       3       0        0             0 grep
Sun Mar 24 09:50:28 2019 kern.err kernel: [ 1781.938643] Out of memory: Kill process 4032 (opkg) score 103 or sacrifice child
Sun Mar 24 09:50:28 2019 kern.err kernel: [ 1781.946605] Killed process 4032 (opkg) total-vm:5784kB, anon-rss:2924kB, file-rss:4kB, shmem-rss:0kB
Sun Mar 24 09:50:29 2019 daemon.err uhttpd[1692]: WARNING: opkg file "/var/opkg-lists/gargoyle" does not exist or can not be opened
Sun Mar 24 09:50:29 2019 daemon.err uhttpd[1692]: Killed

After attempting to install a new plugin:

Code: Select all

Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.555038] procd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=0, order=0, oom_score_adj=0
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.566712] CPU: 0 PID: 1 Comm: procd Not tainted 4.9.156 #0
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.572787] Stack : 804c76c2 00000030 00000000 00000001 8182c294 80455267 804096c8 00000001
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.581317]         804c3800 8181fd10 00000001 00200000 00000000 800a96bc 00000000 00000004
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.590108]         00000006 80476624 8040d16c 8181fb8c 00000000 800d786c 804c76c2 00000073
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.599317]         00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.607826]         00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.616555]         ...
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.619033] Call Trace:
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.621509] [<8006b220>] show_stack+0x70/0x8c
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.626610] [<801185ac>] dump_header.isra.5+0x6c/0x160
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.631819] [<800dd338>] oom_kill_process+0xa8/0x438
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.637092] [<800ddc10>] out_of_memory+0x3c4/0x3e8
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.641942] [<800e1314>] __alloc_pages_nodemask+0x924/0x9ac
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.647590] [<800dbf30>] filemap_fault+0x400/0x5c4
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.653141] [<800fc788>] __do_fault+0x174/0x230
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.657777] [<800ffec8>] handle_mm_fault+0x448/0xb2c
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.662954] [<8007155c>] __do_page_fault+0x23c/0x468
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.668005] [<80065f80>] ret_from_exception+0x0/0x10
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.672994] Mem-Info:
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.676119] active_anon:1910 inactive_anon:9 isolated_anon:0
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.676119]  active_file:138 inactive_file:187 isolated_file:1
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.676119]  unevictable:0 dirty:0 writeback:0 unstable:0
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.676119]  slab_reclaimable:199 slab_unreclaimable:1542
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.676119]  mapped:8 shmem:142 pagetables:73 bounce:0
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.676119]  free:250 free_pcp:0 free_cma:0
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.708722] Node 0 active_anon:7640kB inactive_anon:36kB active_file:552kB inactive_file:748kB unevictable:0kB isolated(anon):0kB isolated(file):4kB mapped:32kB dirty:0kB writeback:0kB shmem:568kB writeback_tmp:0kB unstable:0kB pages_scanned:0 all_unreclaimable? yes
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.733297] Normal free:1012kB min:1024kB low:1280kB high:1536kB active_anon:7640kB inactive_anon:36kB active_file:552kB inactive_file:748kB unevictable:0kB writepending:0kB present:32768kB managed:27636kB mlocked:0kB slab_reclaimable:796kB slab_unreclaimable:6168kB kernel_stack:376kB pagetables:292kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Sun Mar 24 09:37:09 2019 kern.emerg kernel: lowmem_reserve[]: 0 0
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.768957] Normal: 24*4kB (UM) 15*8kB (UME) 50*16kB (UME) 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 1016kB
Sun Mar 24 09:37:09 2019 kern.emerg kernel: 468 total pagecache pages
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.784132] 0 pages in swap cache
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.787503] Swap cache stats: add 0, delete 0, find 0/0
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.793479] Free swap  = 0kB
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.796435] Total swap = 0kB
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.799328] 8192 pages RAM
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.802047] 0 pages HighMem/MovableOnly
Sun Mar 24 09:37:09 2019 kern.warn kernel: [  981.806911] 1283 pages reserved
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.810081] [ pid ]   uid  tgid total_vm      rss nr_ptes nr_pmds swapents oom_score_adj name
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.819236] [  481]     0   481      296       15       3       0        0             0 ubusd
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.827962] [  489]     0   489      225       10       3       0        0             0 askfirst
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.837640] [ 1112]     0  1112      306       27       4       0        0             0 logd
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.846875] [ 1185]     0  1185      266       10       3       0        0             0 dropbear
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.856440] [ 1265] 65534  1265      290       16       3       0        0             0 portmap
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.865291] [ 1293]     0  1293      430       43       4       0        0             0 netifd
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.874739] [ 1446]     0  1446      302       10       3       0        0             0 udhcpc
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.883762] [ 1477]     0  1477      303       12       4       0        0             0 ntpd
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.893045] [ 1692]     0  1692      798       53       5       0        0             0 uhttpd
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.901870] [ 2042]     0  2042      498       31       4       0        0             0 hostapd
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.911100] [ 2373]     0  2373      303       11       3       0        0             0 crond
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.920454] [ 3339]   453  3339      642      339       4       0        0             0 dnsmasq
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.929357] [ 3598]     0  3598      283       25       3       0        0             0 dropbear
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.938799] [ 3607]     0  3607      302       10       3       0        0             0 ash
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.947868] [ 3674]     0  3674      311       26       4       0        0             0 haserl
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.956961] [ 3675]     0  3675      317       25       4       0        0             0 sh
Sun Mar 24 09:37:09 2019 kern.info kernel: [  981.965369] [ 3680]     0  3680     1820     1108       5       0        0             0 gpkg
Sun Mar 24 09:37:09 2019 kern.err kernel: [  981.974553] Out of memory: Kill process 3680 (gpkg) score 156 or sacrifice child
Sun Mar 24 09:37:09 2019 kern.err kernel: [  981.982316] Killed process 3680 (gpkg) total-vm:7280kB, anon-rss:4428kB, file-rss:4kB, shmem-rss:0kB
Sun Mar 24 09:37:10 2019 daemon.err uhttpd[1692]: Killed
Sun Mar 24 09:37:58 2019 daemon.err uhttpd[1692]: WARNING: opkg file "/var/opkg-lists/openwrt_18.06-snapshot_packages" does not exist or can not be opened
Sun Mar 24 09:37:58 2019 daemon.err uhttpd[1692]: WARNING: opkg file "/var/opkg-lists/openwrt_18.06-snapshot_base" does not exist or can not be opened
Sun Mar 24 09:37:58 2019 daemon.err uhttpd[1692]: No packages to install.
Sun Mar 24 09:37:58 2019 daemon.err uhttpd[1692]:
Sun Mar 24 09:37:58 2019 kern.info kernel: [ 1032.942683] do_page_fault(): sending SIGSEGV to gpkg for invalid read access from 00000000
Sun Mar 24 09:37:58 2019 kern.info kernel: [ 1032.951066] epc = 775b6519 in libericstools.so.1[775b4000+14000]
Sun Mar 24 09:37:58 2019 kern.info kernel: [ 1032.957520] ra  = 775b65d3 in libericstools.so.1[775b4000+14000]
Sun Mar 24 09:37:58 2019 daemon.err uhttpd[1692]: Segmentation fault
Sun Mar 24 09:38:16 2019 kern.info kernel: [ 1048.304143] do_page_fault(): sending SIGSEGV to hostapd for invalid write access to 00000000
Sun Mar 24 09:38:16 2019 kern.info kernel: [ 1048.312776] epc = 778ac33c in libc.so[77884000+92000]
Sun Mar 24 09:38:16 2019 kern.info kernel: [ 1048.317929] ra  = 0041ca11 in wpad[400000+b0000]
Sun Mar 24 09:38:27 2019 kern.info kernel: [ 1061.397148] br-lan: port 2(wlan0) entered disabled state
Sun Mar 24 09:38:27 2019 daemon.notice netifd: Network device 'wlan0' link is down
Sun Mar 24 09:38:27 2019 kern.info kernel: [ 1062.012495] device wlan0 left promiscuous mode
Sun Mar 24 09:38:27 2019 kern.info kernel: [ 1062.017550] br-lan: port 2(wlan0) entered disabled state
Sun Mar 24 09:38:44 2019 user.notice mac80211: Failed command: iw phy phy0 set antenna all all
Sun Mar 24 09:38:46 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Sun Mar 24 09:38:46 2019 daemon.notice hostapd: rfkill: Cannot open RFKILL control device

Another one that seems to crop up here and there:

Code: Select all

Sun Mar 24 09:38:58 2019 daemon.err uhttpd[1692]: sh: write error: Broken pipe
Sun Mar 24 09:38:58 2019 daemon.err uhttpd[1692]: sh: write error: Broken pipe
Sun Mar 24 09:38:58 2019 daemon.err uhttpd[1692]: sh: write error: Broken pipe
Sun Mar 24 09:38:58 2019 daemon.err uhttpd[1692]: sh: write error: Broken pipe
Sun Mar 24 09:38:58 2019 daemon.err uhttpd[1692]: sh: write error: Broken pipe
Sun Mar 24 09:38:58 2019 daemon.err uhttpd[1692]: sh: write error: Broken pipe
Success

Otherwise there seems to be enough room for the plugins themselves, this is with a couple additional plugins installed:

Code: Select all

Root Drive 960.000 kBytes Total, 560.000 kBytes Free

Any ideas?

ispyisail
Moderator
Posts: 4875
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by ispyisail »

I think some of your problems have been addressed in 1.11.0.x

viewtopic.php?f=14&t=11941

try a new version then report back

RomanHK
Posts: 667
Joined: Sat May 04, 2013 4:18 pm
Location: Czech Republik

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by RomanHK »

@Daeron
Yes, most problems are related to memory like: "Out of memory: Kill process ...", I do not recommend using AdBlock and other plugins. The CPU is also slow and therefore the transmission speed is extremely slow, nothing can be done about it. Beta 1.11.X by @ispyisail might help you troubleshoot WiFi issues like "Failed command: iw phy phy0 set antenna all all ..."

My recommendation:
1. Try beta version 1.11.X
2. Don't use Adblock plugins and others
3. Return to version 1.9 or 1.10, which is not so demanding and consider buying a new stronger router.

Unfortunately, I own 1043ND v2 and I have to be satisfied with version 1.10 - these routers are not so powerful and with OpenWrt 17.01 it is bad.

So I'm sorry I didn't help better ...
Turris Omnia with Gargoyle 1.12.0
Linksys WRT3200ACM with Gargoyle 1.12.0
TL-WR1043ND v2 with Gargoyle 1.10.0

ispyisail
Moderator
Posts: 4875
Joined: Mon Apr 06, 2009 3:15 am
Location: New Zealand

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by ispyisail »

Yes, most problems are related to memory like


Agree, didn't think about that.

4MB routers were giving us problems now the 8MB are starting to do the same :(

Note: Old firmware have security problems so if your worried about that get a new router.

Lantis
Moderator
Posts: 5709
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by Lantis »

In this case it is not the flash memory that is the issue, it is the RAM.
You can try to remove all of the Openwrt package feeds and leave only the Gargoyle ones, this should reduce the memory footprint of gpkg.

A better solution is to use a USB stick to add more plugin storage, and to use part of this as swap space to alleviate RAM congestion.
I cut down the USB plugin to the bare minimum to allow people to perform this step before adding anything else to their router.

When I return I’ll look at reducing the memory usage of gpkg, but swap/external plugin root is the solution.
(This is also causing slow page loads by the way).
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

Daeron
Posts: 28
Joined: Mon Oct 31, 2016 5:30 am

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by Daeron »

Thanks for all the responses!

I realize the device is fairly weak by now, but probably will still be adequate for my needs for some time. I just wasn't sure if 1.11 is expected to have a larger footprint in general which would explain the problems cropping up now (as opposed to just some obscure bug triggering).

I will try the various potential solutions and see what works (beta version, disabling adblock/plugin sources, downgrading etc).

Lantis, do you have some instructions on the exact steps required to set up the swap space from start to finish?

Also it appears to me that the GUI only allows adding but not removing plugin sources, so might need some instructions on that as well.

raven
Posts: 33
Joined: Mon Mar 25, 2019 12:25 am

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by raven »

I install 1.11.0 on glar150 from factory and I configure automatic reboot on the router at 1.00AM everyday. After reboot the router dhcp server function failed to distribute the ip address to lan and wifi. I have to manually power off and on to make the router dhcp server function back to normal. Does anyone experience something similar?

RomanHK
Posts: 667
Joined: Sat May 04, 2013 4:18 pm
Location: Czech Republik

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by RomanHK »

raven wrote:I install 1.11.0 on glar150 from factory and I configure automatic reboot on the router at 1.00AM everyday. After reboot the router dhcp server function failed to distribute the ip address to lan and wifi. I have to manually power off and on to make the router dhcp server function back to normal. Does anyone experience something similar?

This will not be a problem in reebot (reboot is the same as turning off and turning on the router) - a new boot system from scratch.

It will probably be caused by the fact that you do not reset the switch during reboot and thus the LAN connection is not interrupted and therefore there is no new registration in DHCP. But it's just my guess.

I do not recommend rebooting every day because the DHCP table of the reservations is cleared and this can cause a collision of IP addresses on the network.

EDIT: I've got an idea yet. Set each client static reservation according to MAC address, so that clients will always have the same IP address after deleting DHCP table. This ensures that there is no IP collision after reboot.
Last edited by RomanHK on Mon Mar 25, 2019 5:45 am, edited 1 time in total.
Turris Omnia with Gargoyle 1.12.0
Linksys WRT3200ACM with Gargoyle 1.12.0
TL-WR1043ND v2 with Gargoyle 1.10.0

raven
Posts: 33
Joined: Mon Mar 25, 2019 12:25 am

Re: Version 1.11.0 : Based on OpenWrt 18.06

Post by raven »

RomanHK wrote:
raven wrote:I install 1.11.0 on glar150 from factory and I configure automatic reboot on the router at 1.00AM everyday. After reboot the router dhcp server function failed to distribute the ip address to lan and wifi. I have to manually power off and on to make the router dhcp server function back to normal. Does anyone experience something similar?

This will not be a problem in reebot (reboot is the same as turning off and turning on the router) - a new boot system from scratch.

It will probably be caused by the fact that you do not reset the switch during reboot and thus the LAN connection is not interrupted and therefore there is no new registration in DHCP. But it's just my guess.

I do not recommend rebooting every day because the DHCP table of the reservations is cleared and this can cause a collision of IP addresses on the network.


I forgot to mention that before using 1.11.0, I had used 1.10.0 for some time and found no problem with dhcp function even though I rebooted it every day. And now I reverted back to 1.10.0 again because of the dhcp problem i found in 1.11.0

Post Reply