Fwd: dbus-monitor from remote PC (Win7 machie)

kishore <[email protected]>
Newsgroups gmane.comp.freedesktop.dbus
Message-ID <CAGF=DOha=WByONQbbPYF3ifLomb8-4=NeoWMnL+tPi9JX7pQoA@mail.gmail.com> 
Hi All,

Can any one help to solve my problem.

I wanted to see the dbus messages of UBUNTU machine from windows machine by
running the dbus-monitor from window7. for that i had done the below
entries in /etc/dbus-1/session.conf

  <listen>tcp:host=localhost,bind=*,port=6669</listen>
  <listen>unix:tmpdir=/tmp</listen>
  <auth>ANONYMOUS</auth>
  <allow_anonymous/>

In windows machine i had created the DBUS_SESSION_BUS_ADDRESS environment
variable with value as tcp:host=10.90.82.120,port=6669. to get more dbus
message in windows
i have created the DBUS_VERBOSE environment variable and value is "1".

I just ran the dbus-monitor.exe from windows 7. it shows me below error.

"Failed to open connection to session message bus: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken."

can any one help on this i had spent two days to solve this.

Ubuntu machine : 10.4 lts
IP : 10.90.82.120
DBUS :
test@HP-xw4600-Workstation:/etc/dbus-1$ dbus-daemon --version
D-Bus Message Bus Daemon 1.6.18
Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.


Windows 7 IP : 10.90.82.104

DBUS_VERBOSE = log file(dbus-monitor_verbosity.txt) attached when i ran the
dbus-monitor.exe.

1. Am i doing wrong or missing anything here ?
2. If any other process is their please let me know ?

Appreciate
​your ​
help on my problem.

Thanks,
Kishore

_______________________________________________
dbus mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dbus
dbus-monitor_verbosity.txt (text/plain, 7 KB) 
D:\CONNECTIVITY_TESTING\DbusLibrary>dbus-monitor.exe
8524: Filling in system bus address...
8524:   used default system bus "tcp:host=localhost,port=12434"
8524: Filling in session bus address...
8524:   "tcp:host=10.90.82.120,port=6669"
8524: Filling in activation bus address...
8524:   "none set"
8524: opening shared connection to: tcp:host=10.90.82.120,port=6669
8524: checking for existing connection
8524: creating shared_connections hash table
8524:   successfully created shared_connections
Family none
8524: Successfully connected to tcp socket 10.90.82.120:6669
8524: _dbus_getsid() returns 1
8524: client: going from state NeedSendAuth to state WaitingForData
8524: Initialized transport on address tcp:host=10.90.82.120,port=6669
8524: FIXME: implement _dbus_disable_sigpipe (void)
8524:   LOCK: _dbus_connection_new_for_transport
8524:   UNLOCK: protected_change_watch
8524:   LOCK: protected_change_watch
8524:   UNLOCK: protected_change_watch
8524:   LOCK: protected_change_watch
8524: check_read_watch: fd = 140
8524:   setting read watch enabled = 0
8524:   UNLOCK: protected_change_watch
8524:   LOCK: protected_change_watch
8524: check_write_watch(): needed = 1 on connection 0281E7F0 watch 0281E5B0 fd = 140 outgoing messages exist 0
8524:   UNLOCK: protected_change_watch
8524:   LOCK: protected_change_watch
8524:   UNLOCK: _dbus_connection_new_for_transport
8524:   LOCK: _dbus_connection_open_internal
8524:   UNLOCK: _dbus_connection_open_internal
8524: Allocated slot 0 on allocator 1008037C total 1 slots allocated 1 used
8524:   LOCK: dbus_connection_get_data
8524:   UNLOCK: dbus_connection_get_data
8524:   LOCK: dbus_connection_set_data
8524:   UNLOCK: dbus_connection_set_data
8524:   LOCK: dbus_connection_send_with_reply
8524: Allocated slot 0 on allocator 100803C0 total 1 slots allocated 1 used
8524:   UNLOCK: protected_change_timeout
8524:   LOCK: protected_change_timeout
8524: Message 0281EDF8 (1 /org/freedesktop/DBus org.freedesktop.DBus Hello '') for org.freedesktop.DBus added to outgoing queue 0281E7F0, 1 pending to send
8524: Message 0281EDF8 serial is 1
8524: _dbus_connection_do_iteration_unlocked start
8524:   UNLOCK: _dbus_connection_acquire_io_path
8524: _dbus_connection_acquire_io_path locking io_path_mutex
8524: _dbus_connection_acquire_io_path start connection->io_path_acquired = 0 timeout = 0
8524: _dbus_connection_acquire_io_path end connection->io_path_acquired = 1 we_acquired = 1
8524: _dbus_connection_acquire_io_path unlocking io_path_mutex
8524:   LOCK: _dbus_connection_acquire_io_path
8524: Transport iteration flags 0x1 timeout -1 connected = 1
8524:  iteration flags = write timeout = -1 read_watch = 0281E5E0 write_watch = 0281E5B0 fd = 140
8524: select: to=0
        W:140 E:140

select: = 1:
        W:140
in iteration, need_read=0 need_write=1
8524: exchange_credentials: do_reading = 0, do_writing = 1
8524: send: len=1 fd=140
8524: send: = 1
8524: wrote 1 zero byte, credential sending isn't implemented yet
8524:  client auth state: bytes to send
8524: send: len=106 fd=140
8524: send: failed: Software caused connection abort
8524: Error writing to remote app: Software caused connection abort
8524: _dbus_transport_disconnect start
8524: socket_disconnect
8524: free_watches start
8524:   UNLOCK: protected_change_watch
8524:   LOCK: protected_change_watch
8524: Setting watch fd -1 data to data = 00000000 function = 00000000 from data = 00000000 function = 00000000
8524:   UNLOCK: protected_change_watch
8524:   LOCK: protected_change_watch
8524: Setting watch fd -1 data to data = 00000000 function = 00000000 from data = 00000000 function = 00000000
8524: free_watches end
8524: _dbus_close_socket: socket=140,
8524: _dbus_transport_disconnect end
8524: check_read_watch: fd = -1
8524: Not authenticated, not writing anything
8524:  ... leaving do_iteration()
8524: _dbus_transport_do_iteration end
8524: _dbus_connection_release_io_path locking io_path_mutex
8524: _dbus_connection_release_io_path start connection->io_path_acquired = 1
8524: _dbus_connection_release_io_path unlocking io_path_mutex
8524: _dbus_connection_do_iteration_unlocked end
8524: dispatch status = complete is_connected = 0
8524: Dropping 1 outgoing messages since we're disconnected
8524: Message 0281EDF8 (1 /org/freedesktop/DBus org.freedesktop.DBus Hello '') removed from outgoing queue 0281E7F0, 0 left to send
8524: Sending disconnect message from notify_disconnected_and_dispatch_complete_unlocked
8524: Synthesized message 0281EF10 added to incoming queue 0281E7F0, 1 incoming
8524:   UNLOCK: protected_change_timeout
8524:   LOCK: protected_change_timeout
8524:   UNLOCK: _dbus_connection_unlock
8524:   LOCK: free_pending_call_on_hash_removal
8524:   UNLOCK: _dbus_connection_unlock
8524:   LOCK: connection_timeout_and_complete_all_pending_calls_unlocked
8524: Synthesized message 0281E888 added to incoming queue 0281E7F0, 2 incoming
8524:   UNLOCK: _dbus_connection_update_dispatch_status_and_unlock
8524:   LOCK: dbus_connection_unref
8524:   UNLOCK: dbus_connection_unref
8524:   LOCK: _dbus_connection_lock
8524:   UNLOCK: _dbus_connection_unlock
8524:   LOCK: _dbus_connection_lock
8524:   UNLOCK: _dbus_connection_unlock
8524:   LOCK: _dbus_connection_lock
8524: _dbus_connection_flush_unlocked middle
8524: dbus_connection_send_with_reply_and_block(): will block 25000 milliseconds for reply serial 1 from 1437569922 sec 993394 usec to 1437569947 sec 993394 usec
8524: check_for_reply_and_update_dispatch_unlocked checked for reply
8524: dbus_connection_send_with_reply_and_block(): got reply
8524:   handing message 0281EF10 (error) to pending call serial 1
8524:   UNLOCK: _dbus_connection_unlock
8524:   LOCK: _dbus_connection_lock
8524:   UNLOCK: _dbus_connection_unlock
8524:   LOCK: check_for_reply_and_update_dispatch_unlocked
8524:   UNLOCK: _dbus_connection_update_dispatch_status_and_unlock
8524:   LOCK: dbus_connection_unref
8524:   UNLOCK: dbus_connection_unref
8524:   LOCK: _dbus_connection_lock
8524:   UNLOCK: _dbus_connection_unlock
8524:   LOCK: _dbus_connection_lock
8524:   UNLOCK: _dbus_connection_unlock
8524:   LOCK: _dbus_connection_lock
8524:   UNLOCK: _dbus_connection_unlock
8524: Freeing slot 0 on allocator 100803C0 total 1 allocated 1 used
8524:   LOCK: dbus_connection_unref
8524:   UNLOCK: dbus_connection_unref
8524:   LOCK: _dbus_connection_close_possibly_shared
8524: Disconnecting 0281E7F0
8524: _dbus_transport_disconnect start
8524:   UNLOCK: _dbus_connection_update_dispatch_status_and_unlock
8524:   LOCK: dbus_connection_unref
8524:   UNLOCK: dbus_connection_unref
8524:   LOCK: dbus_connection_unref
8524:   UNLOCK: dbus_connection_unref
8524:   LOCK: dbus_connection_unref
8524:   UNLOCK: dbus_connection_unref
Failed to open connection to session message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

D:\CONNECTIVITY_TESTING\DbusLibrary>
D:\CONNECTIVITY_TESTING\DbusLibrary>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.