FTL offline on Ubuntu 16.04.3 LTS on Vmware ESX 6.5

Please follow the below template, it will help us to help you!

Expected Behaviour:

FTL online in web interface. Statistics available in web interface.

Actual Behaviour:

FTL offline in web interface

No statistics in web interface

FTL Service not running accoring to:
pihole-FTL running
No: Did not find a running FTL process

FTL Service running according to:
service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
_ Loaded: loaded (/etc/init.d/pihole-FTL; bad; vendor preset: enabled)_
_ Active: active (exited) since Tue 2018-01-30 12:37:36 CET; 22h ago_
_ Docs: man:systemd-sysv-generator(8)_
_ Process: 8051 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)_
_ Process: 8058 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)_
_ Tasks: 0_
_ Memory: 0B_
_ CPU: 0_

Jan 30 12:37:36 A*****Q systemd[1]: Starting LSB: pihole-FTL daemon...
Jan 30 12:37:36 A*****Q pihole-FTL[8058]: Not running
Jan 30 12:37:36 A*****Q su[8070]: Successful su for pihole by root
Jan 30 12:37:36 A*****Q su[8070]: + ??? root:pihole
Jan 30 12:37:36 A*****Q su[8070]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jan 30 12:37:36 A*****Q pihole-FTL[8058]: FTL started!
Jan 30 12:37:36 A*****Q systemd[1]: Started LSB: pihole-FTL daemon.

Pihole functionality working and blocking ads.

Using: Ubuntu 16.04.3 LTS on Vmware ESX 6.5
2 vCPU and 16GB ram.
Running Apache for serving 200 OK response on ads on second ip on interface.
Running lighttpd for admin web interface pihole on primary ip on interface.
Pihole is listening on primary ip on interface.

After flushing logs and restarting pihole-FTL webinterface and pihole-FTL work for a short time and then pihole-FTL fails.

Debug Token:

Unable to upload log:
* Using openssl for transmission.
[βœ—] There was an error uploading your debug log.
_ * Please try again or contact the Pi-hole team for assistance._
_ * A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log_

Any help is very much appreciated.

edit (20180131 13:21):
Just ran pihole-FTL debug and pihole-FTL crashed with below error:
*** stack smashing detected ***: pihole-FTL terminated
Aborted (core dumped)

Should I use the fix in this post?:

Can you give some of the lines of the backtrace?

Yes, and please don't run pihole -up afterwards, even if that is suggested

If I follow this (GitHub - pi-hole/FTL: The Pi-hole FTL engine) debugging process as my current (non root) user.
I see these errors:

2018-02-01 07:17:00.084] save_to_DB() - SQL error (8): attempt to write a readonly database
[2018-02-01 07:17:00.084] save_to_DB() - SQL error (8): attempt to write a readonly database
[2018-02-01 07:17:00.085] save_to_DB() - SQL error (8): attempt to write a readonly database
[2018-02-01 07:17:00.085] save_to_DB() - exiting due to too many errors
[2018-02-01 07:17:00.085] Notice: Queries stored in DB: 0
[2018-02-01 07:17:00.085] There are queries that have not been saved

But the process keeps running

It crashed with these last lines:

[New Thread 0x7ffff4ac1700 (LWP 8364)]
[Thread 0x7ffff4ac1700 (LWP 8364) exited]
[New Thread 0x7ffff4ac1700 (LWP 8367)]
[Thread 0x7ffff4ac1700 (LWP 8367) exited]
[New Thread 0x7ffff4ac1700 (LWP 8370)]
[Thread 0x7ffff4ac1700 (LWP 8370) exited]
[New Thread 0x7ffff4ac1700 (LWP 8385)]
[New Thread 0x7fffe7fff700 (LWP 8386)]
[Thread 0x7ffff4ac1700 (LWP 8385) exited]
[Thread 0x7fffe7fff700 (LWP 8386) exited]
[New Thread 0x7fffe7fff700 (LWP 8389)]
[Thread 0x7fffe7fff700 (LWP 8389) exited]
[New Thread 0x7fffe7fff700 (LWP 8392)]
*** stack smashing detected ***: /usr/bin/pihole-FTL terminated

Thread 146 "client-4" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe7fff700 (LWP 8392)]
0x00007ffff7825428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)

Backtrace:
#0 0x00007ffff7825428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1 0x00007ffff782702a in __GI_abort () at abort.c:89
#2 0x00007ffff78677ea in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7ffff797f49f "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175
#3 0x00007ffff790915c in __GI___fortify_fail (msg=, msg@entry=0x7ffff797f481 "stack smashing detected") at fortify_fail.c:37
#4 0x00007ffff7909100 in __stack_chk_fail () at stack_chk_fail.c:28
#5 0x000055555556c512 in getClientsOverTime (sock=0x7fffe7ffeaf0) at request.c:1155
#6 0x3020302030203020 in ?? ()
#7 0x3020302030203020 in ?? ()
#8 0x3020302030203020 in ?? ()
#9 0x3020302030203020 in ?? ()
#10 0x3020302032203020 in ?? ()
#11 0x3020302030203020 in ?? ()
#12 0x3020302030203020 in ?? ()
#13 0x3020302030203020 in ?? ()
#14 0x3020302030203020 in ?? ()
#15 0x3020302030203020 in ?? ()
#16 0x3020302030203020 in ?? ()
#17 0x3020302030203020 in ?? ()
#18 0x3020302030203020 in ?? ()
#19 0x3020302030203020 in ?? ()
#20 0x3020302031203020 in ?? ()
#21 0x3020302030203020 in ?? ()
#22 0x3020312030203720 in ?? ()
#23 0x3020302030203020 in ?? ()
#24 0x3020302030203020 in ?? ()
#25 0x3020302030203020 in ?? ()
#26 0x3020312030203020 in ?? ()
#27 0x3020392030203020 in ?? ()
#28 0x3020302030203020 in ?? ()
#29 0x3020302033203020 in ?? ()
#30 0x3220302031203020 in ?? ()
#31 0x3020302030203020 in ?? ()
#32 0x3020302030203020 in ?? ()
#33 0x3020342030203020 in ?? ()
#34 0x3320302036203020 in ?? ()
#35 0x2033203020302035 in ?? ()
#36 0x2030203820312038 in ?? ()
#37 0x2037312038332036 in ?? ()
#38 0x3020343120000a31 in ?? ()
#39 0x3020302030203020 in ?? ()
#40 0x2036203031203020 in ?? ()
#41 0x3020363720312030 in ?? ()
#42 0x2030203020313720 in ?? ()
#43 0x2030203020302030 in ?? ()
#44 0x2031203020302030 in ?? ()
#45 0x3631203020302036 in ?? ()
#46 0x2030203031203320 in ?? ()
#47 0x2036332037312030 in ?? ()
#48 0x3134203535203431 in ?? ()
#49 0x3120383120303220 in ?? ()
#50 0x203020000a302031 in ?? ()
#51 0x0a000a3020302030 in ?? ()
#52 0x3020302030200000 in ?? ()
#53 0x3020302030203020 in ?? ()
#54 0x000a302030203020 in ?? ()
#55 0x0a30203020302030 in ?? ()
#56 0x2030000a30203000 in ?? ()
#57 0x2030203020302030 in ?? ()
#58 0x2030203020302030 in ?? ()
#59 0x0a30203020302030 in ?? ()
#60 0x000a30000a302000 in ?? ()
#61 0x0000000000000000 in ?? ()
(gdb)

I installed the patch. Loading clients over time takes a while, but the process keeps on running.

Thanks for the great work!

1 Like

Yes, thanks for trying that out! From your backtrace I see that you have been affected by the same issue another user has reported as well. It will be fixed in the official version with the release that is scheduled to be released shortly.