Home › Forums › FABRIC General Questions and Discussion › error when executing code in slice
- This topic has 5 replies, 3 voices, and was last updated 1 year, 1 month ago by Ilya Baldin.
-
AuthorPosts
-
November 3, 2023 at 12:19 pm #5990HelloI’m working at Rochester Institute of Technology. We have been testing a custom code which we run on the reserved slice.The last couple of days, when we executed the code, it seems to generate some spurious message which results in segmentation error. (see below)This is well tested code (the older version) and it should not be sending the message noted below. Not sure how it is getting generated.ThanksKriti********************In buildIPPublishPacket
Got a new labeltier_addr : 3.1.1.2
ipAddr: 192.168.8.0
Sending MESSAGE_TYPE_PUBLISH_IP_ADD message to – eth1 at
endNWSend Called : eth1Timestamp – 2023-11-03 15:08:18.918812842
Sending MESSAGE_TYPE_PUBLISH_IP_ADD message to – eth2 at
endNWSend Called : eth2Timestamp – 2023-11-03 15:08:18.918834643
tier_addr : 3.1.1.2
Entries : 1
Message V on : eth2
TEST: MNLR Message V received : eth2Timestamp – 2023-11-03 15:08:18.918932057if(<wbr />myTierValue==1)
the action is 1 :
totalEntries = 1TierLen :7 TierAddr: 3.1.1.2
ipLen :4 ipAddr: 192.168.8.0 cidr: 24
Message V on : eth1
TEST: MNLR Message V received : eth1Timestamp – 2023-11-03 15:08:18.919006498if(<wbr />myTierValue==1)
the action is 1 :
totalEntries = 1TierLen :7 TierAddr: 3.1.1.2
ipLen :4 ipAddr: 192.168.8.0 cidr: 24
TEST: MNLR Message 12 received : eth1Timestamp – 2023-11-03 15:08:22.088413454
Message 12 from : 3.1.2.3
Message at tier 1 : Getting the labels for source and destinationResolving ip for destination label : 3.1.2.3Destination interface is : 255.255.255.255
Tier Not Found
ip : 255.255.255.255
ERROR: SIOCGIFINDEX – Misprint Compatibility: No such device
destinationInterfaceIPAddr : 255.255.255.255
ERROR: SIOCGIFHWADDR – Either interface is not correct or disconnected: No such device
ERROR: SIOCGIFINDEX – Misprint Compatibility
ERROR: SIOCGIFHWADDR – Either interface is not correct or disconnected
ERROR: Send failedSegmentation faultNovember 6, 2023 at 3:08 pm #5996Hello Kriti,
Could you please share your Slice ID to help debug this issue?
Thanks,
KomalNovember 7, 2023 at 9:30 am #6023Slice id – acadd67f-3129-4fd7-8d95-9bbf60a3100c
November 7, 2023 at 10:25 am #6026Your slice is up and running – all VMs and services are up. Please verify that the network interfaces exist under the names you expect in all the VMs. We generally cannot help you with your custom application, but the error suggests the application is trying to use a network interface that for some reason is not there or is not in the ‘up’ state. Please validate the low level functionality of the slice (e.g. the node reachability) before starting your application.
November 7, 2023 at 10:38 am #6028I am using ssh commands to login into each node, then manually checking each node is up and all the interfaces are up, all interfaces are up then trying to execute my code. Still it is showing me the same error.
November 7, 2023 at 10:59 am #6031Hello,
Please inspect your application configuration or try to add debugging output – since this is your custom application we can only provide limited assistance. If a slice is operating as expected at the Operating System level the rest is generally considered experimenter’s responsibility.
-
AuthorPosts
- You must be logged in to reply to this topic.