Can the MB event log be accessed w/o System tab? **solved**

[johnn]

I have a situation where the System tab cannot be accessed, and times out, but other tabs can be accessed and the device is generally working.

Is there some other way to see the event log, in case it contains hints for the System Tab problem?

More details...
viewtopic.php?f=56&t=10548

[admin]

Please solve your root cause problem. It is not making sense to invent work arounds for this and that.
My offer to help you by inspecting your system is still on the table.

[johnn]

Please solve your root cause problem. It is not making sense to invent work arounds for this and that.
My offer to help you by inspecting your system is still on the table.

That is precisely what I am trying to do.

It is my understanding that I have to get to the System tab to give you access to the device, and I have no access to the System tab.

If I can give you access to the device I would be more than happy to do that!

[admin]

In that case just add the line "xlogin 1" to the file "/root/meteobridge.conf" and reboot.
What I need on top is the MAC of your Meteobridge (see sticker on back or ask "ifconfig" from linux shell).

[johnn]

In that case just add the line "xlogin 1" to the file "/root/meteobridge.conf" and reboot.
What I need on top is the MAC of your Meteobridge (see sticker on back or ask "ifconfig" from linux shell).

"xlogin 1" added.
MAC: 60:E3:27:25:2F:AE

[admin]

Thanks, I can login. Root cause is that your DNS server is not able to handle DNS reverse look ups,
which is needed by "route" command that identifies gateway IP for Meteobridge.

When I try to make a reverse lookup of your Gateway IP it takes 40 seconds (before it runs into a time out)!

Code: Select all

root@MeteoBridge:~# time nslookup 10.1.1.1
Server:    10.1.1.1
Address 1: 10.1.1.1

Name:      10.1.1.1
Address 1: 10.1.1.1
real	0m 40.02s
user	0m 0.00s
sys	0m 0.01s

Next update will have a code change to avoid this kind of reverse lookups, but you might see problems like this with other equipment in your LAN as well.

[johnn]

Ahha! Thank you very much for that. I will look into this situation, and my options. Is there any idea of the schedule for the new release?

I am left wondering why it worked initially.

Thanks, I can login. Root cause is that your DNS server is not able to handle DNS reverse look ups,
which is needed by "route" command that identifies gateway IP for Meteobridge.

When I try to make a reverse lookup of your Gateway IP it takes 40 seconds (before it runs into a time out)!

Code: Select all

root@MeteoBridge:~# time nslookup 10.1.1.1
Server:    10.1.1.1
Address 1: 10.1.1.1

Name:      10.1.1.1
Address 1: 10.1.1.1
real	0m 40.02s
user	0m 0.00s
sys	0m 0.01s

Next update will have a code change to avoid this kind of reverse lookups, but you might see problems like this with other equipment in your LAN as well.

[admin]

It is even worse. Regular DNS lookups also take tons of time and drive upload services into timeouts.

Code: Select all

root@MeteoBridge:~# time ping -c 1 weatherstation.wunderground.com
PING weatherstation.wunderground.com (38.102.137.157): 56 data bytes
64 bytes from 38.102.137.157: seq=0 ttl=44 time=194.870 ms

--- weatherstation.wunderground.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 194.870/194.870/194.870 ms
real	0m 15.39s
user	0m 0.00s
sys	0m 0.01s

15 seconds to resolve the WU domain is not acceptable.

I recommend to change to a static IP setting on "Network" tab and to use "8.8.8.8" as DNS server, "10.1.1.1" should remain the gateway, mask "255.255.255.0" is fine as long as you are in a class C network.

BTW: Your MAC is added to the beta program, so you have the most recent updates already installed.

[johnn]

I recommend to change to a static IP setting on "Network" tab and to use "8.8.8.8" as DNS server, "10.1.1.1" should remain the gateway, mask "255.255.255.0" is fine as long as you are in a class C network.
BTW: Your MAC is added to the beta program, so you have the most recent updates already installed.

I have switched to 8.8.8.8 and we are going fine.
Thank you very much for your assistance.