How to watch subscribers from icebox?

[yinghaoyu]

Using vim to open the file named subscribers with garbled characters.

[pepone]

Hi @yinghaoyu

Can you please tell us the path and the repository of the file?

[pepone]

Sorry for the delay.

You can use the icestormadmin command to list the subscribers for each topic.

See https://doc.zeroc.com/ice/3.7/ice-services/icestorm/icestorm-administration

You can do the same programmatically using the TopicManager and Topic interfaces

ice/slice/IceStorm/IceStorm.ice

Line 85 in 5c68ccc

interface Topic

Note 3.4.2 is out of support, you should consider upgrading to 3.7 release.

Cheers,
Jose

[yinghaoyu]

Thanks for your reply.
Sorry for the version I had mentioned above. 3.6.2 is the correct version being used. But it seems not working by using icestormadmin -e topics. It shows as below,

!! 06/12/24 16:42:12.096 icestormadmin: error: IPEndpointI.cpp:429: Ice::EndpointParseException:error while parsing endpoint `no argument provided for -p option in endpoint `tcp  -p -t 3000''

[pepone]

As the error says you are using an invalid -p option in your endpoint. -p requires and argument see https://doc.zeroc.com/ice/3.7/client-side-features/proxies/proxy-and-endpoint-syntax

[yinghaoyu]

$ cat config.service

#
# This property is used by the administrative client to connect to IceStorm.
#
#IceStorm.TopicManager.Proxy=MonitorIceStorm/TopicManager:default -p 9999

Ice.Default.EncodingVersion=1.0

# This property defines the endpoints on which the IceStorm
# TopicManager listens.
#
IceStorm.TopicManager.Endpoints=default -p 9999

#
# The IceStorm service instance name.
#
IceStorm.InstanceName=MonitorIceStorm

#
# This property defines the endpoints on which the topic
# publisher objects listen. If you want to federate
# IceStorm instances this must run on a fixed port (or use
# IceGrid).
#
IceStorm.Publish.Endpoints=tcp -p 10001:udp -p 10001

#
# TopicManager Tracing
#
# 0 = no tracing
# 1 = trace topic creation, subscription, unsubscription
# 2 = like 1, but with more detailed subscription information
#
IceStorm.Trace.TopicManager=2

#
# Topic Tracing
#
# 0 = no tracing
# 1 = trace unsubscription diagnostics
#
IceStorm.Trace.Topic=1

#
# Subscriber Tracing
#
# 0 = no tracing
# 1 = subscriber diagnostics (subscription, unsubscription, event
#     propagation failures)
#
IceStorm.Trace.Subscriber=1

#
# Flush Tracing (for batch mode transfer flushing)
#
# 0 = no tracing
# 1 = trace activity of flusher thread
#
#IceStorm.Trace.Flush=1

#
# Amount of time in milliseconds between flushes for batch mode
# transfer. The minimum allowable value is 100ms.
#
IceStorm.Flush.Timeout=2000

#
# Network Tracing
#
# 0 = no network tracing
# 1 = trace connection establishment and closure
# 2 = like 1, but more detailed
# 3 = like 2, but also trace data transfer
#
Ice.Trace.Network=3
Ice.Trace.ThreadPool=1

#
# This property defines the home directory of the Freeze
# database environment for the IceStorm service.
#
Freeze.DbEnv.IceStorm.DbHome=db

Freeze.DbEnv.IceStorm.DbHome=db specifies the db path, and the file named subscribers is in this db directory.

As you can see in this file, IceStorm.TopicManager.Endpoints had already been set. I have no cure about the errors.

[pepone]

icestormadmin does not use IceStorm.TopicManager.Endpoints, you probably want to use IceStormAdmin.TopicManager.Default see the linked doc for details.