starting failed!
starting failed!
error during operation pread http://repo.moka5.com/fearless/ver-12/local.ckdsk 196608-197533: failed writing received data to disk/application: Input/output error
I have tried the both the LivePC Engine Windows and the Bare Metal version and I get the above error when I try to start.
Although I can browse and subscribe to other LivePCs they do not appear to be buffering at all.
I am currently most interested in the Bare Metal version so I will start with it. I do not have this problem from home only at work and since the problem appears on multiple machines with different configurations I believe the problem may be associated with our Hardware Firewall (SonicWall).
The firewall is Logging IMPC Echo Reply from moka5 servers but according to it's settings not blocking them (set to Log Only).
Any ideas on what allowances I need to make to get moka5 working without opening up the firewall more than necessary?
Some of the firewall logs: (I am not sure how to get the LivePC logs in the Bare Metal version.)
6 01/24/2007 11:38:43.720 Alert Intrusion Prevention IPS Detection Alert: ICMP Echo Reply, SID: 316, Priority: Low 216.93.180.88, 8, WAN, m1.sfo1.moka5.com 10.#.#.#, 42761, LAN
7 01/24/2007 11:37:42.944 Alert Intrusion Prevention IPS Detection Alert: ICMP Echo Reply, SID: 316, Priority: Low 216.93.180.88, 8, WAN, m1.sfo1.moka5.com 10.#.#.#, 29704, LAN
9 01/24/2007 11:36:41.880 Alert Intrusion Prevention IPS Detection Alert: ICMP Echo Reply, SID: 316, Priority: Low 216.93.180.88, 8, WAN, m1.sfo1.moka5.com 10.#.#.#, 11271, LAN
I can
I can access the link.
http://repo.moka5.com/fearless/ver-11/vm.vmx
I get:
checkpoint.vmState = ""
config.version = "8"
displayname = "Fearless Browser"
ethernet0.address = "00:0c:29:df:b6:0d"
ethernet0.addresstype = "generated"
ethernet0.connectiontype = "nat"
ethernet0.generatedAddress = "00:0c:29:d7:a7:f7"
ethernet0.generatedAddressOffset = "0"
ethernet0.present = "true"
.......
I will try looking at the logs...
We've contact the user
We've contact the user directly to gather additional information about the SonicWall and provided additional to monitor.
Please add to this forum topic if you also have a SonicWall Firwall.
Kevin
Fixed with Kevin's Help
After several messages back and forth Kevin determined that range requests were not being supported through the Sonicwall.
This is the default configuration for sonicwalls with Gateway antivirus enabled.
There is a potential vulnerability to this but if you want to change this you can do so by selecting Enable HTTP Byte-Range request with Gateway AV check box on the Internal Settings page of the SonicWALL configuration tool.
This can usually be found by logging in to your sonicwall and then changing the url to http://(sonicwallIP)/diag.html. Select Internal Settings and check the appropriate box.
Joe
This is an interesting
This is an interesting issue. I'll check with my peers on this issue.
Does this also fail when accessing via the browser?
http://repo.moka5.com/fearless/ver-11/vm.vmx
The baremetal log are available in /cache/log/
Use F5 to open terminal
Kevin