forum.pistar.uk

I just upgraded my Pi-Star to v4.1.0 RC7. I SSH into it VIA Tera Term and made some changes to that I need for my setup, and when I try to go back to read only I see this.

rpi-ro
mount: /: mount point is busy.
pi-star@pi-star(rw):~$ rpi-ro
mount: /: mount point is busy.
pi-star@pi-star(rw):~$

Any Ideas?


I am also seeing these messages in the syslog quite frequently..


Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN
Feb 22 22:24:53 pi-star minissdpd[754]: peer 192.168.1.155:1900 is not from a LAN


Any thing to be concerned with?

Thanks
Ed
AK7AN

AK7AN wrote: ↑Sat Feb 22, 2020 10:36 pm I just upgraded my Pi-Star to v4.1.0 RC7. I SSH into it VIA Tera Term and made some changes to that I need for my setup, and when I try to go back to read only I see this.

rpi-ro
mount: /: mount point is busy.
pi-star@pi-star(rw):~$ rpi-ro
mount: /: mount point is busy.
pi-star@pi-star(rw):~$

Any Ideas?

Getting stuck in R/W mode seems to be a common problem -- often I'll connect to mine and find that the overnight refresh has done something that leaves the root mount point "busy".
to reboot tends to reset it to R/O

My apologies... please accept.

Any info on the other messages I am seeing. They happen once a minute..
Thanks
Ed
AK7AN

I don't have anything connected to my LAN with that IP address. My DHCP server assigns from 1.2 to 1.51 a total of 50 available addresses. I have shut off multiple devices connected to my network and I am still seeing that. I will keep investigating. Strange, before I upgraded to the most recent version of Pi-Star I did not see that in the syslog.
Thanks
Ed
AK7AN

This is what I get when I ping it with the ping test in my router
This is what I get when I do a trace route


Would that show that the IP address of 192.168.1.155 is coming from the 64.77.244.1? If so that is coming from outside of my LAN.

I believe that I have solved it. I have my LAN setup with 2 Linksys E1200 routers. One of them is the main router that is the DHCP server, and the other is just setup as an access point. The 192.168.1.155 must be the IP link between the 2 routers. If I disconnect the #2 router the message in the syslog of the Pi stops. As soon as I reconnect it starts again. I did verify that the MAC address of that IP was Cisco/Linksys.
Thanks again
Ed
AK7AN