Issue Details (XML | Word | Printable)

Key: SFOS-1079
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Steve Loughran
Reporter: Steve Loughran
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
SmartFrog

entry points could report network connectivity problems better

Created: 23/Jan/09 05:37 PM (GMT)   Updated: 23/Jan/09 10:37 PM (GMT)
Return to search
Component/s: .sfCore
Affects Version/s: 3.17.004
Fix Version/s: 3.17.010

Time Tracking:
Not Specified

Environment:
Home, desktop PC running linux, trying to talk to a VMWare image of Centos running on a nearby laptop, connected by ethernet. LAN is a private 192.168.2.1 DNS, laptop is an out-the-box Centos image with minimal customisation and hostname set to localhost.localnet, IPAddr given by the DHCP server in the wifi box. There is no DNS server on this network.

Compatibility: backwards compatible


 Description  « Hide
When sfPing fails it could be more helpful

2009/01/23 17:32:28:483 GMT [WARN ][main] SFCORE_LOG - SmartFrog security is NOT active
 - FAILED when trying PING of '-v', host:192.168.1.6
    Result:
      * Exception: 'Unable to connect to sfDaemon on: 192.168.1.6.
        Reason: sfDaemon may not be running on 192.168.1.6java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
         java.net.ConnectException: Connection refused'


1. Prettier layout
2. Better stack trace (how?)

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.