but it never shuts down. Any idea of how to fix this?Unmounting local filessystems...umount2: Device or ressource busy
umount: /data: device is busy
umount2: Device or resource busy
umount: /data: device is busy
failed.
Will now halt.
Shutdown: hda
Cannot shutdown/reboot Meteohub on VirtualBox
Moderator: Mattk
Cannot shutdown/reboot Meteohub on VirtualBox
When issuing a shutdown or poweroff from the commandline, Debian fails with:
- YJB
- Platinum Boarder
- Posts: 387
- Joined: Thu Feb 19, 2009 5:53 pm
- Location: Venhuizen, Netherlands
- Contact:
Re: Cannot shutdown/reboot Meteohub on VirtualBox
I'm running on Virtualbox as well, and have not experienced this kind of issue.
Sounds like a process is not being killed.
Might want to check with
which process is using the filesystem.
Sounds like a process is not being killed.
Might want to check with
Code: Select all
fuser /data
Re: Cannot shutdown/reboot Meteohub on VirtualBox
Hi,
fuser /data does not show any processes at all
.
I also have an issue with Meteohub halts the datacollection from my Oregion WMR100 + RFXcom. It looses connection all together and seems to crash somehow.. Despite the VM saying "stopping", it never stops so I need to reboot the host PC.
Out of curiosity which OS do you use for you VirtualBox? I'm on Ubuntu 12.04 LTS.
I was also looking into upgrading Debian (to "Lenny" I think), as I thought a newer version was better for virtualization, but I don't know if it would help.
fuser /data does not show any processes at all

I also have an issue with Meteohub halts the datacollection from my Oregion WMR100 + RFXcom. It looses connection all together and seems to crash somehow.. Despite the VM saying "stopping", it never stops so I need to reboot the host PC.
Out of curiosity which OS do you use for you VirtualBox? I'm on Ubuntu 12.04 LTS.
I was also looking into upgrading Debian (to "Lenny" I think), as I thought a newer version was better for virtualization, but I don't know if it would help.
- YJB
- Platinum Boarder
- Posts: 387
- Joined: Thu Feb 19, 2009 5:53 pm
- Location: Venhuizen, Netherlands
- Contact:
Re: Cannot shutdown/reboot Meteohub on VirtualBox
Hi,
My virtual host is Opensuse
Virtualbox is 4.1.32. Yes, I know it's old, but I do not have the guts/time to upgrade and it runs pretty stable (4 guest environments including MH).
I'm using, amongst other, RFXcom and I do not have disconnect issues.
My virtual host is Opensuse
Code: Select all
(openSUSE 12.3 (x86_64)
VERSION = 12.3
CODENAME = Dartmouth
I'm using, amongst other, RFXcom and I do not have disconnect issues.
Re: Cannot shutdown/reboot Meteohub on VirtualBox
I'm on Vbox 4.3.20, so the latest but it seems strange that a new version shouldn't work
.
Did you convert the VMware image as I did? I haven't changed any settings afterwards but maybe there's bit and pieces which should be altered in the VM. Of course Meteohub is upgraded to the latest version and the entire configuration from my ALIX.1D has been restored on the VM version.

Did you convert the VMware image as I did? I haven't changed any settings afterwards but maybe there's bit and pieces which should be altered in the VM. Of course Meteohub is upgraded to the latest version and the entire configuration from my ALIX.1D has been restored on the VM version.
- YJB
- Platinum Boarder
- Posts: 387
- Joined: Thu Feb 19, 2009 5:53 pm
- Location: Venhuizen, Netherlands
- Contact:
Re: Cannot shutdown/reboot Meteohub on VirtualBox
Hmm, I can't remember the exact steps.
This is how my config currently looks like:
This is what I gathered from my notes (after getting the VM up and running):
This is how my config currently looks like:
Code: Select all
VBoxManage showvminfo Meteohub
Name: Meteohub
Guest OS: Debian
UUID: cfba3f0e-1813-43a1-b1ca-2734c1af096c
Config file: /home/vbox/VirtualBox VMs/Meteohub/Meteohub.vbox
Snapshot folder: /home/vbox/VirtualBox VMs/Meteohub/Snapshots
Log folder: /home/vbox/VirtualBox VMs/Meteohub/Logs
Hardware UUID: cfba3f0e-1813-43a1-b1ca-2734c1af096c
Memory size: 256MB
Page Fusion: off
VRAM size: 12MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): HardDisk
Boot Device (2): Not Assigned
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: off
PAE: off
Time offset: 0 ms
RTC: UTC
Hardw. virt.ext: off
Hardw. virt.ext exclusive: on
Nested Paging: off
Large Pages: off
VT-x VPID: on
State: running (since 2014-11-14T09:39:54.180000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Storage Controller Name (0): IDE Controller
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
IDE Controller (0, 0): /home/Virtual/Meteohub/Meteohub-v4.7-4GB.vdi (UUID: 16cc4142-c42f-4a12-9d11-bf7e0c842cb9)
NIC 1: MAC: 000DB90DB3DD, Attachment: Bridged Interface 'eth1', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
Audio: disabled
Clipboard Mode: Bidirectional
Video mode: 720x400x0
VRDE: enabled (Address 0.0.0.0, Ports 4005, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
VRDE port: 4005
Video redirection: disabled
VRDE property: TCP/Ports = "4005"
VRDE property: TCP/Address = <not set>
VRDE property: VideoChannel/Enabled = <not set>
VRDE property: VideoChannel/Quality = <not set>
VRDE property: VideoChannel/DownscaleProtection = <not set>
VRDE property: Client/DisableDisplay = <not set>
VRDE property: Client/DisableInput = <not set>
VRDE property: Client/DisableAudio = <not set>
VRDE property: Client/DisableUSB = <not set>
VRDE property: Client/DisableClipboard = <not set>
VRDE property: Client/DisableUpstreamAudio = <not set>
VRDE property: Client/DisableRDPDR = <not set>
VRDE property: H3DRedirect/Enabled = <not set>
VRDE property: Security/Method = <not set>
VRDE property: Security/ServerCertificate = <not set>
VRDE property: Security/ServerPrivateKey = <not set>
VRDE property: Security/CACertificate = <not set>
VRDE property: Audio/RateCorrectionMode = <not set>
USB: enabled
USB Device Filters:
Index: 0
Active: yes
Name: FTDI FT232R USB UART [0600]
VendorId: 0403
ProductId: 6001
Revision: 0600
Manufacturer: FTDI
Product: FT232R USB UART
Remote: false
Serial Number: A60081IB
Index: 1
Active: no
Name: American Power Conversion Back-UPS 500 FW: 6.4.I USB FW: c1 [0100]
VendorId: 051d
ProductId: 0002
Revision: 0100
Manufacturer: American Power Conversion
Product: Back-UPS 500 FW: 6.4.I USB FW: c1
Remote: false
Serial Number: BB0315008027
Index: 2
Active: no
Name: Unknown device 0a12:0001 [3164]
VendorId: 0a12
ProductId: 0001
Revision: 3164
Manufacturer:
Product:
Remote: false
Serial Number:
Index: 3
Active: no
Name: Unknown device 0a12:0001 [5276]
VendorId: 0a12
ProductId: 0001
Revision: 5276
Manufacturer:
Product:
Remote: false
Serial Number:
Index: 4
Active: no
Name: FTDI FT232R USB UART [0600]
VendorId: 0403
ProductId: 6001
Revision: 0600
Manufacturer: FTDI
Product: FT232R USB UART
Remote:
Serial Number: A4003tNe
Available remote USB devices:
<none>
Currently Attached USB Devices:
UUID: 5d56b154-c6d9-419d-9bca-b9d6f0641cff
VendorId: 0x0403 (0403)
ProductId: 0x6001 (6001)
Revision: 6.0 (0600)
Manufacturer: FTDI
Product: FT232R USB UART
SerialNumber: A60081IB
Address: sysfs:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5.1//device:/dev/vboxusb/002/015
Shared folders: <none>
VRDE Connection: not active
Clients so far: 0
Guest:
Configured memory balloon size: 0 MB
OS type: Debian
Additions run level: 0
Guest Facilities:
Facility "Seamless Mode": not active (last update: 2014/11/14 21:39:46 UTC)
Facility "Graphics Mode": active/running (last update: 2014/11/14 21:39:46 UTC)
Code: Select all
## Meteohub-VM
- Stop logging on the alix1d
- Stop logging on the VM
- Disconnect the RFXcom
- alix1d # scp -rp /data/* root@meteohub-vm:/data
- alix1d # meteohub scp -rp "/home/meteohub/meteohub.conf root@meteohub-vm:"/home/meteohub/meteohub.conf
- Add all the crontab entries inside the meteohub marked boundaries
- Connect the RFXcom to the VM
- Reboot meteohub-vm and resume operations
Re: Cannot shutdown/reboot Meteohub on VirtualBox
Thanks!
There's a couple of differences between our configs. I'm not sure what the impact is:
So there's absolutely a couple of areas which I could look into. I've just created a new VM with Meteohub and did not restore the backup. This seems to be more stable, so maybe there's a config issue somewhere.. Thanks so far!
There's a couple of differences between our configs. I'm not sure what the impact is:
Mine is offACPI: on
Mine is onPAE: off
Mine is notRTC: UTC
MIne is onNested Paging: off
Mine is enabledVideo redirection: disabled
So there's absolutely a couple of areas which I could look into. I've just created a new VM with Meteohub and did not restore the backup. This seems to be more stable, so maybe there's a config issue somewhere.. Thanks so far!
Re: Cannot shutdown/reboot Meteohub on VirtualBox
Hmm, doesn't seem to work very well. E.g. if I restart data logging it always ends up saying:

The only thing I cannot seem to change which you have disabled is the "Acceleration VT-x/AMD-V" which I need to have enabled, otherwise Meteohub doesn't start at all. Might turn out, than I need to go back to the hardwarebox afterall
and I need to restart the entire VirtualBoxerror receive data from socket 127.0.0.1:5555: Resource temporarily unavailable
Warning: Data logging has been halted.

The only thing I cannot seem to change which you have disabled is the "Acceleration VT-x/AMD-V" which I need to have enabled, otherwise Meteohub doesn't start at all. Might turn out, than I need to go back to the hardwarebox afterall

Re: Cannot shutdown/reboot Meteohub on VirtualBox
I seem to have found the problem, which relates to my Oregon WMR100N station. Whenever that is connected and used my Meteohub, I experience a lot of problems, like cannot reboot, data logging fails etc.
By the looks of it, Meteohub does not close the connection properly so /data "hangs" at shutdown and I cannot stop/start data logging.
@Boris: Is this something you perhaps could look into?
By the looks of it, Meteohub does not close the connection properly so /data "hangs" at shutdown and I cannot stop/start data logging.
@Boris: Is this something you perhaps could look into?
- YJB
- Platinum Boarder
- Posts: 387
- Joined: Thu Feb 19, 2009 5:53 pm
- Location: Venhuizen, Netherlands
- Contact:
Re: Cannot shutdown/reboot Meteohub on VirtualBox
Hi,
I would say 1st look at the USB side of things: like a different cable, a shorter cable, use an USB hub.
I'm also not sure what your setup is: initially your were referring to RFXcom, now it appears to be a "plain"connection to the weather station?
I would say 1st look at the USB side of things: like a different cable, a shorter cable, use an USB hub.
I'm also not sure what your setup is: initially your were referring to RFXcom, now it appears to be a "plain"connection to the weather station?
Re: Cannot shutdown/reboot Meteohub on VirtualBox
Hi,
Actually I have both my WMR100 and RFXCOM connected (WMR is better at picking up the PCR800 rain sensor + it has barometer), but RFXCOM is more stable + better range, so I combine the two.
The cable was also used when my WMR was connected directly to ALIX.1D and it worked without problems (so did Meteohub
), but I could try to find another. It's pretty clear that things go wrong when the WMR is connected.
Actually I have both my WMR100 and RFXCOM connected (WMR is better at picking up the PCR800 rain sensor + it has barometer), but RFXCOM is more stable + better range, so I combine the two.
The cable was also used when my WMR was connected directly to ALIX.1D and it worked without problems (so did Meteohub
