Page 1 of 1

[Help] F5-422 / TOS 6.0.673 = NETWORK SETTINGS PROBLEMS ( MENU - Interface = EMPTY with only Pop-up "Configuration..."

Posted: 21 May 2025, 05:31
by battantho
Hello I

[Help] F5-422 / TOS 6.0.673 = NETWORK SETTINGS PROBLEMS ( MENU - Interface = EMPTY with only Pop-up "Configuration in progress, please wait!"

Image

I don't see my networks interface and I try a lot of things to resolve this problem but nothing work !!

I houve any ideas to solve my problem !!

Image

Image

PS : I have an other PROBLEM to CREATE a NEW VPN CONNECTION = I have a ERROR MESSAGE "Configuration not save" but my last VPN CONNECTION with same parameters of the "NEW" has work very well with no problem.

I Don't Think if my 2 problems are LINKS or NO !!!

Re: [Help] F5-422 / TOS 6.0.673 = NETWORK SETTINGS PROBLEMS ( MENU - Interface = EMPTY with only Pop-up "Configuration..

Posted: 21 May 2025, 09:22
by MikeZhang
Hi dear friend, could you generate system log and send to support at terra-master.com?

Re: [Help] F5-422 / TOS 6.0.673 = NETWORK SETTINGS PROBLEMS ( MENU - Interface = EMPTY with only Pop-up "Configuration..

Posted: 23 May 2025, 03:39
by battantho
hello

i have already send my system log :
mar. 20 mai 07:09 by email and NO REPONSE

Re: [Help] F5-422 / TOS 6.0.673 = NETWORK SETTINGS PROBLEMS ( MENU - Interface = EMPTY with only Pop-up "Configuration..

Posted: 23 May 2025, 10:22
by TMnick
battantho wrote: 23 May 2025, 03:39
Hello, we have received your system logs and will investigate the issue as soon as possible. We will notify you immediately once we have a result (expected to take 1-2 days). We sincerely apologize for any inconvenience caused.

Re: [Help] F5-422 / TOS 6.0.673 = NETWORK SETTINGS PROBLEMS ( MENU - Interface = EMPTY with only Pop-up "Configuration..

Posted: 24 Jul 2025, 04:12
by pongo
Same here with F4-423 / TOS 6.0.750

systemd-networkd.service: Main process exited, code=exited, status=127/n/a
Jul 23 21:33:48 TNAS systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Jul 23 21:33:48 TNAS systemd[1]: Failed to start Network Configuration.
Jul 23 21:33:48 NAS systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1.
Jul 23 21:33:48 NAS systemd[1]: Stopped Network Configuration.
Jul 23 21:33:48 NAS systemd[1]: Starting Network Configuration...
Jul 23 21:33:48 NAS systemd[2643215]: systemd-networkd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied

systemctl status dbus
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static)
Active: active (running) since Tue 2025-07-15 17:14:41 CEST; 1 week 1 day ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
Main PID: 631 (dbus-daemon)
Tasks: 1 (limit: 18947)
Memory: 1.8M
CPU: 13.724s
CGroup: /system.slice/dbus.service
└─631 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

Jul 23 22:04:38 TNAS dbus-daemon[631]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.serv
ice' requested by ':1.454' (uid=0 pid=2623184 comm="/usr/sbin/TOSDaemon ")
Jul 23 22:05:03 TNAS dbus-daemon[631]: [system] Failed to activate service 'org.freedesktop.resolve1': timed out (service_start_
timeout=25000ms)
Jul 23 22:05:03 TNAS dbus-daemon[631]: [system] Activating via systemd: service name='org.freedesktop.network1' unit='dbus-org.freedesktop.network1.serv
ice' requested by ':1.455' (uid=0 pid=2623184 comm="/usr/sbin/TOSDaemon ")
Jul 23 22:05:28 TNAS dbus-daemon[631]: [system] Failed to activate service 'org.freedesktop.network1': timed out (service_start_
timeout=25000ms)
Jul 23 22:05:28 TNAS dbus-daemon[631]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.serv
ice' requested by ':1.456' (uid=0 pid=2623184 comm="/usr/sbin/TOSDaemon ")
Jul 23 22:05:53 TNAS dbus-daemon[631]: [system] Failed to activate service 'org.freedesktop.resolve1': timed out (service_start_
timeout=25000ms)
Jul 23 22:05:53 TNAS dbus-daemon[631]: [system] Activating via systemd: service name='org.freedesktop.network1' unit='dbus-org.freedesktop.network1.serv
ice' requested by ':1.457' (uid=0 pid=2623184 comm="/usr/sbin/TOSDaemon ")
Jul 23 22:06:18 TNAS dbus-daemon[631]: [system] Failed to activate service 'org.freedesktop.network1': timed out (service_start_
timeout=25000ms)
Jul 23 22:06:18 TNAS dbus-daemon[631]: [system] Activating via systemd: service name='org.freedesktop.network1' unit='dbus-org.freedesktop.network1.serv
ice' requested by ':1.458' (uid=0 pid=2623184 comm="/usr/sbin/TOSDaemon ")
Jul 23 22:06:43 TNAS dbus-daemon[631]: [system] Failed to activate service 'org.freedesktop.network1': timed out (service_start_
timeout=25000ms)

Re: [Help] F5-422 / TOS 6.0.673 = NETWORK SETTINGS PROBLEMS ( MENU - Interface = EMPTY with only Pop-up "Configuration..

Posted: 24 Jul 2025, 18:53
by TMnight
Is there still a problem with the TOS 6.0.750 network service? Is it the same problem as after TOS 6.0.673?
Please execute the following command in the terminal and take a screenshot

Code: Select all

cat /etc/.default.sys

Re: [Help] F5-422 / TOS 6.0.673 = NETWORK SETTINGS PROBLEMS ( MENU - Interface = EMPTY with only Pop-up "Configuration..

Posted: 25 Jul 2025, 02:51
by pongo
cat /etc/.default.sys
[system]
console = 5
defaultgwdev = eth0
Autofan = 1
Fanspeed = 4
dateformat = %Y/%m/%d
timezone = Amsterdam
timezone_php = Europe/Amsterdam
timeformat = 24
timemode = 1
timespace = 10
timeserver = pool.ntp.org
demo = 0
demouser = admin,terramaster
mailconfig = 0
sslhttp = 0
spindown = 0
PowerSet = 1
apphost = https://app.terra-master.com
boardcast = 1
checkAndDownload = 0
Beta = 0
debugModel = false
debugModelLogVolume =

Re: [Help] F5-422 / TOS 6.0.673 = NETWORK SETTINGS PROBLEMS ( MENU - Interface = EMPTY with only Pop-up "Configuration..

Posted: 25 Jul 2025, 09:59
by TMnight
pongo wrote: 25 Jul 2025, 02:51
The configuration seems to be normal. If the problem you described still exists, please make an appointment with an engineer remotely in the official website online chat. For the engineer to understand the problem, please attach the link to this forum