search

BroadbandForum / obuspa

OB-USP-AGENT is a system daemon providing a User Services Platform (USP) Agent. https://github.com/BroadbandForum/obuspa/wiki
BSD 3-Clause "New" or "Revised" License
93 stars 62 forks source link

Issue with connecting the OBUSPA agent to a controller #84

Closed 4briltorres closed 1 year ago

4briltorres commented 1 year ago

I'm having trouble connecting with the OBUSPA agent and a controller demo using STOMP. This is what I'm getting in the Wireshark capture. I think the controller is requesting data from Device.DeviceInfo, but the agent is not responding.

subscription:0
content-length:317
message-id:2147522982
destination:obuspa-agent
expires:0
redelivered:false
priority:4
persistent:false
timestamp:1684423764672
content-type:application/vnd.bbf.usp.msg
reply-to-dest:controller-notify-dest
__AMQ_CID:19954bfe
fromUmp:1
.1.0..os::012345-0800279C2A56:.....
(
$dadb50f1-e5ac-4156-9175-cefcb7620f71.....
..
..
!Device.DeviceInfo.ManufacturerOUI
.Device.DeviceInfo.SerialNumber
!Device.DeviceInfo.SoftwareVersion
.Device.DeviceInfo.ModelName
.Device.DeviceInfo.Manufacturer
.Device.DeviceInfo.ProductClass
!Device.DeviceInfo.HardwareVersion.
MESSAGE
subscription:0
content-length:317
message-id:2147522984
destination:obuspa-agent
expires:0
redelivered:false
priority:4
persistent:false
timestamp:1684423764673
content-type:application/vnd.bbf.usp.msg
reply-to-dest:controller-notify-dest
__AMQ_CID:c260665d
fromUmp:1
.1.0..os::012345-0800279C2A56:.....
(
$7a0576cd-ff11-4b25-b0d9-2e74338cab1d.....
..
..
!Device.DeviceInfo.ManufacturerOUI
.Device.DeviceInfo.SerialNumber
!Device.DeviceInfo.SoftwareVersion
.Device.DeviceInfo.ModelName
.Device.DeviceInfo.Manufacturer
.Device.DeviceInfo.ProductClass
!Device.DeviceInfo.HardwareVersion.
MESSAGE
subscription:0
content-length:317
message-id:2147522986
destination:obuspa-agent
expires:0
redelivered:false
priority:4
persistent:false
timestamp:1684423764673
content-type:application/vnd.bbf.usp.msg
reply-to-dest:controller-notify-dest
__AMQ_CID:c0e5acd4
fromUmp:1
.1.0..os::012345-0800279C2A56:.....
(
$10242324-8aa2-4b59-be73-16c4936820d0.....
..
..
!Device.DeviceInfo.ManufacturerOUI
.Device.DeviceInfo.SerialNumber
!Device.DeviceInfo.SoftwareVersion
.Device.DeviceInfo.ModelName
.Device.DeviceInfo.Manufacturer
.Device.DeviceInfo.ProductClass
!Device.DeviceInfo.HardwareVersion.

SEND
content-length:135
content-type:application/vnd.bbf.usp.msg
reply-to-dest:obuspa-agent
destination:ump./stechs/.cpe-1
.1.2..os::012345-0800279C2A56:g.e
.Event-2023-05-18T15:30:24Z-3...A
?B=
.PeriodicEventsSubscription..
.Device.LocalAgent..    Periodic!.

This is what I'm getting in the console: log.txt

In factory_reset_example.txt, I added these lines to test:

Device.DeviceInfo.ManufacturerOUI "AABBCC"
Device.DeviceInfo.SerialNumber "ZTEEQFEHCP02862"
Device.DeviceInfo.SoftwareVersion "V1.0.10P1T16"
Device.DeviceInfo.ModelName "F670E"
Device.DeviceInfo.Manufacturer "ZTE"
Device.DeviceInfo.ProductClass "ZTE1234"
Device.DeviceInfo.HardwareVersion "V1.0"

I'm probably skipping a step or need to configure something in the vendor settings.

holme-r commented 1 year ago

Two errors stand out from the log: "attempt to write a readonly database" -> permissions issue ? "host=....." -> Device.STOMP.Connection.1.Host is not configured correctly

Don't forget that you need to delete out the database, if you want changes from the factory reset file to take effect.

holme-r commented 1 year ago

For the "attempt to write a read only database" issue, if you're using the /tmp directory to store your USP DB then one possible cause might be: https://unix.stackexchange.com/questions/691441/root-cannot-write-to-file-that-is-owned-by-regular-user

johnblackford commented 1 year ago

Closing as there has been no further discussion - please re-open if this is still an issue.