MB Pro Uptime

[caddguru]

I purchased my MB Pro just before Christmas 2016. Installation and setup has been very easy and this would be a great device if I could guarantee that it will run for more than a few days at a time without needing a reboot.

My MB Pro does not seem to be stable beyond about 3 days. It typically needs a reboot every 2-3 days. I usually notice this when I receive the courtesy email from WU that my device has stopped sending data.

Any guidance please on things to look for. I would like to see what can be done to resolve this as soon as possible.

Is there anyway of scheduling the device to reboot itself.?

Regards
Mike

[Ian.]

Mike,

I had a similar situation which needed the MBP be returned to Germany for repair, this was done very swiftly once Boris had had a look at the logs via Remote dial in to determine the issue.

Ian

[caddguru]

Ian

Many thanks for your swift reply and guidance.

Boris... Happy for you to take a look at the logs! Looking forward to receiving contact from you.

Regards
Mike

[admin]

Please send remote login URL and password to "info(at)meteobridge.com".
Procedure how to allow remote login is explained in the FAQ:
viewtopic.php?f=57&t=9885

[admin]

Thanks for login details. I can't see a hardware issue from the logs.

What puzzles me is that WLAN seems to be rather unstable.
Kernel log tells me that connection drops from time to time and
that it takes many tries to establish again.

Code: Select all

[34777.310000] wlan0: authenticate with 1c:49:7b:62:a3:11
[34777.320000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[34777.330000] wlan0: authenticated
[34777.340000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[34777.340000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[34777.350000] wlan0: associated
[72803.310000] wlan0: authenticate with 1c:49:7b:62:a3:11
[72803.320000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[72803.340000] wlan0: authenticated
[72803.350000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[72803.360000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[72803.360000] wlan0: associated
[72909.310000] wlan0: authenticate with 1c:49:7b:62:a3:11
[72909.320000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[72909.620000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 2/3)
[72909.630000] wlan0: authenticated
[72909.640000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[72909.650000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[72909.660000] wlan0: associated
[72929.300000] wlan0: authenticate with 1c:49:7b:62:a3:11
[72929.310000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[72929.320000] wlan0: authenticated
[72929.330000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[72929.340000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[72929.340000] wlan0: associated
[73195.290000] wlan0: authenticate with 1c:49:7b:62:a3:11
[73195.300000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[73195.320000] wlan0: authenticated
[73195.330000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[73195.340000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[73195.350000] wlan0: associated
[73220.300000] wlan0: authenticate with 1c:49:7b:62:a3:11
[73220.310000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[73220.320000] wlan0: authenticated
[73220.330000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[73220.340000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[73220.340000] wlan0: associated
[73930.980000] wlan0: authenticate with 1c:49:7b:62:a3:11
[73930.990000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[73931.000000] wlan0: authenticated
[73931.010000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[73931.020000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[73931.030000] wlan0: associated
[74033.300000] wlan0: authenticate with 1c:49:7b:62:a3:11
[74033.310000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[74033.320000] wlan0: authenticated
[74033.330000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[74033.340000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[74033.350000] wlan0: associated
[74062.310000] wlan0: authenticate with 1c:49:7b:62:a3:11
[74062.320000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[74062.330000] wlan0: authenticated
[74062.340000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[74062.340000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[74062.350000] wlan0: associated
[74101.280000] wlan0: authenticate with 1c:49:7b:62:a3:11
[74101.290000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 1/3)
[74101.590000] wlan0: send auth to 1c:49:7b:62:a3:11 (try 2/3)
[74101.610000] wlan0: authenticated
[74101.620000] wlan0: associate with 1c:49:7b:62:a3:11 (try 1/3)
[74101.620000] wlan0: RX AssocResp from 1c:49:7b:62:a3:11 (capab=0x431 status=0 aid=2)
[74101.630000] wlan0: associated

Signal strength is a -54db which should be ok. Is the WiFi router/ap restarting from time to time?
Problems might be associated with router drop outs.

[caddguru]

Admin

Thanks for taking a look at the logs so swiftly. We have recently had new broadband installed and since then I have had wifi issues on my work laptop. However nobody else in the household seems to experience the same an issue.

However, I will report the wifi issue to my BB provider (they also supply the router) In the meantime I will connect the MB Pro to the LAN.

I will report on progress with this potential fix as the week goes by.

You mention a potential hardware issue? Is this related?

Many thanks again for your help.

Regards
Mike

[caddguru]

MB Pro is now on the LAN. Access details should be as previously advised,

[water8600]

Hi all

I searched the forum because we observed the same issue and looking for a solution.
After a couple of days of successful operation the unit is no longer accessible over our internal network.
It is also not answering to ping's. On the display the IP address is still the same and has not changed, The unit has now a fix IP in our network because we thougth lease time or something else might be the reason for hanging.

In the log we observed periodical connectivy loss and we can not not explain that from our WLAN point of view. Many other devices are running in that segment without any issues.

• ....
  Tue Feb 14 14:54:48 2017 kern.info kernel: [20484.950000] wlan0: disassociated from f0:b2:e5:dc:9e:a0 (Reason: 1)
  Tue Feb 14 14:54:48 2017 daemon.notice netifd: Network device 'wlan0' link is down
  Tue Feb 14 14:54:48 2017 daemon.notice netifd: Interface 'wlan' has link connectivity loss
  Tue Feb 14 14:54:49 2017 kern.info kernel: [20485.730000] wlan0: authenticate with f0:b2:e5:dc:9e:a0
  Tue Feb 14 14:54:49 2017 kern.info kernel: [20485.740000] wlan0: send auth to f0:b2:e5:dc:9e:a0 (try 1/3)
  Tue Feb 14 14:54:49 2017 kern.info kernel: [20485.750000] wlan0: authenticated
  Tue Feb 14 14:54:49 2017 kern.info kernel: [20485.760000] wlan0: associate with f0:b2:e5:dc:9e:a0 (try 1/3)
  Tue Feb 14 14:54:49 2017 kern.info kernel: [20485.760000] wlan0: RX AssocResp from f0:b2:e5:dc:9e:a0 (capab=0x1431 status=0 aid=57)
  Tue Feb 14 14:54:49 2017 kern.info kernel: [20485.770000] wlan0: associated
  Tue Feb 14 14:54:49 2017 daemon.notice netifd: Network device 'wlan0' link is up
  Tue Feb 14 14:54:49 2017 daemon.notice netifd: Interface 'wlan' has link connectivity
  Tue Feb 14 15:24:59 2017 kern.info kernel: [22295.850000] wlan0: disassociated from f0:b2:e5:dc:9e:a0 (Reason: 1)
  Tue Feb 14 15:24:59 2017 daemon.notice netifd: Network device 'wlan0' link is down
  Tue Feb 14 15:24:59 2017 daemon.notice netifd: Interface 'wlan' has link connectivity loss
  Tue Feb 14 15:24:59 2017 kern.info kernel: [22296.650000] wlan0: authenticate with f0:b2:e5:dc:9e:a0
  Tue Feb 14 15:24:59 2017 kern.info kernel: [22296.660000] wlan0: send auth to f0:b2:e5:dc:9e:a0 (try 1/3)
  Tue Feb 14 15:25:00 2017 kern.info kernel: [22296.670000] wlan0: authenticated
  Tue Feb 14 15:25:00 2017 kern.info kernel: [22296.680000] wlan0: associate with f0:b2:e5:dc:9e:a0 (try 1/3)
  Tue Feb 14 15:25:00 2017 kern.info kernel: [22296.680000] wlan0: RX AssocResp from f0:b2:e5:dc:9e:a0 (capab=0x1431 status=0 aid=71)
  Tue Feb 14 15:25:00 2017 kern.info kernel: [22296.690000] wlan0: associated
  Tue Feb 14 15:25:00 2017 daemon.notice netifd: Network device 'wlan0' link is up
  Tue Feb 14 15:25:00 2017 daemon.notice netifd: Interface 'wlan' has link connectivity
  Tue Feb 14 15:55:10 2017 kern.info kernel: [24106.750000] wlan0: disassociated from f0:b2:e5:dc:9e:a0 (Reason: 1)
  Tue Feb 14 15:55:10 2017 daemon.notice netifd: Network device 'wlan0' link is down
  Tue Feb 14 15:55:10 2017 daemon.notice netifd: Interface 'wlan' has link connectivity loss
  Tue Feb 14 15:55:10 2017 kern.info kernel: [24107.530000] wlan0: authenticate with f0:b2:e5:dc:9e:a0
  Tue Feb 14 15:55:10 2017 kern.info kernel: [24107.540000] wlan0: send auth to f0:b2:e5:dc:9e:a0 (try 1/3)
  Tue Feb 14 15:55:10 2017 kern.info kernel: [24107.550000] wlan0: authenticated
  Tue Feb 14 15:55:10 2017 kern.info kernel: [24107.560000] wlan0: associate with f0:b2:e5:dc:9e:a0 (try 1/3)
  Tue Feb 14 15:55:10 2017 kern.info kernel: [24107.570000] wlan0: RX AssocResp from f0:b2:e5:dc:9e:a0 (capab=0x1431 status=0 aid=82)
  Tue Feb 14 15:55:10 2017 kern.info kernel: [24107.570000] wlan0: associated
  .....

Any help is welcome, The configuartion file is available on demand.

Cheers