Spread daemon crashes at Create_form1() "INSERT HOLE 1" line
Kyle Hsieh (謝名凱) <[email protected]> Thu, 11 Jul 2013 20:00:11 +0800
| Newsgroups | gmane.network.spread.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Spread team, We encountered a problem about spread daemon crashes. The spread.conf and log file are attached. >From the log, we found spread daemon continuously dump "INSERT HOLE1" messages and then crashes. This problem happens randomly once/twice a week. Unfortunately, we cannot get the debug dump file for you to analyze. We will do our best to provide any other info for you which may help to analyze this problem. Thank you! Best regards, Kyle Hsieh Software R&D Department, Industrial Video Networking (IVN) Division Moxa Inc. Tel : +886 2 89191230 ext.1673 Fax: +886 2 89191231 [email protected] This email and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this email. Any unauthorized duplication, utilization, disclosure, or distribution of the material in this email and its attached files is strictly forbidden. _______________________________________________ Spread-users mailing list [email protected] http://lists.spread.org/mailman/listinfo/spread-users
image001.png
(image/png, 5.3 KB) - not displayed
spread.conf
(application/octet-stream, 3 KB)
###############################
## Speard Configuration File ##
###############################
## The following segment is necessary for spread to work correctly.
## Example:
## Spread_Segment <multicast_address>:<port> {
## "<machine_name>" <machine_address>
## }
Spread_Segment 192.168.255.255:4803 {
"192.168.1.11" 192.168.1.11
"192.168.1.21" 192.168.1.21
"192.168.1.31" 192.168.1.31
"192.168.2.11" 192.168.2.11
"192.168.2.21" 192.168.2.21
"192.168.2.31" 192.168.2.31
}
#Set what internal Spread events are logged to the screen or file
# (see EventLogFile).
# Default setting is to enable PRINT and EXIT events only.
#The PRINT and EXIT types should always be enabled. The names of others are:
# EXIT PRINT DEBUG DATA_LINK NETWORK PROTOCOL SESSION
# CONFIGURATION MEMBERSHIP FLOW_CONTROL STATUS EVENTS
# GROUPS MEMORY SKIPLIST ALL NONE
# ALL and NONE are special and represent either enabling every type
# or enabling none of them.
# You can also use a "!" sign to negate a type,
# so { ALL !DATA_LINK } means log all events except data_link ones.
## Uncomment the following line to control debug message format.
DebugFlags = { PRINT EXIT NETWORK SESSION CONFIGURATION MEMBERSHIP STATUS GROUPS }
#Set whether to log to a file as opposed to stdout/stderr and what
# file to log to.
# Default is to log to stdout.
#
#If option is not set then logging is to stdout.
#If option is set then logging is to the filename specified.
# The filename can include a %h or %H escape that will be replaced at runtime
# by the hostname of the machine upon which the daemon is running.
# For example "EventLogFile = spreadlog_%h.log" with 2 machines
# running Spread (machine1.mydomain.com and machine2.mydomain.com) will
# cause the daemons to log to "spreadlog_machine1.mydomain.com.log" and
# "spreadlog_machine2.mydomain.com.log" respectively.
## Uncomment the following line to create log file.
EventLogFile = spread_%h.log
#Set whether to add a timestamp in front of all logged events or not.
# Default is no timestamps. Default format is "[%a %d %b %Y %H:%M:%S]".
#If option is commented out then no timestamp is added.
#If option is enabled then a timestamp is added with the default format
#If option is enabled and set equal to a string, then that string is used
# as the format string for the timestamp. The string must be a valid time
# format string as used by the strftime() function.
#EventTimeStamp
# or
#EventTimeStamp = "[%a %d %b %Y %H:%M:%S]"
EventTimeStamp = "[%Y/%m/%d %H:%M:%S]"
#Set whether to add a precise (microsecond) resolution timestamp to all logged
# events or not. This option requires that EventTimeStamp is also enabled.
# If the option is commented out then the microsecond timestamp is not added
# If the option is uncommented then a microsecond time will print in addition
# to the H:M:S resolution timestamp provided by EventTimeStamp.
EventPreciseTimeStamp
spread.log
(application/octet-stream, 420.5 KB) - not displayed