View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000006 | easycwmp | Help | public | 2014-08-26 20:41 | 2014-10-01 17:03 |
| Reporter | thejimi | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| OS | Linux | OS Version | Mint 17 | ||
| Summary | 0000006: Unable to get easycwmp to connect to ACS, likely a problem with ubus | ||||
| Description | I set up easycwmp via the documentation which was straight forward. I start up ubus via the command per instructions: /usr/sbin/ubusd -s /tmp/ubus.sock But running easycwmp, I get the log: config_init_local(53):: easycwmp.@local[0].interface=eth0 config_init_local(63):: easycwmp.@local[0].port=7647 config_init_local(81):: easycwmp.@local[0].ubus_socket=/var/run/ubus.sock config_init_local(69):: easycwmp.@local[0].username=easycwmp config_init_local(75):: easycwmp.@local[0].password=easycwmp config_init_acs(147):: easycwmp.@acs[0].scheme=http config_init_acs(153):: easycwmp.@acs[0].username=pico config_init_acs(159):: easycwmp.@acs[0].password=pico config_init_acs(165):: easycwmp.@acs[0].hostname=192.168.6.25 config_init_acs(175):: easycwmp.@acs[0].port=7547 config_init_acs(181):: easycwmp.@acs[0].path=/ config_init_acs(187):: easycwmp.@acs[0].periodic_enable=1 config_init_acs(193):: easycwmp.@acs[0].periodic_interval=100 main(279): ubus initialization failed +++ HTTP SERVER CONFIGURATION +++ ip: '192.168.6.18' port: '7647' --- HTTP SERVER CONFIGURATION --- +++ HTTP CLIENT CONFIGURATION +++ http_client_init(49):: url: http://pico:pico@192.168.6.25:7547/ http_client_init(55):: ssl_verify: SSL certificate validation disabled. --- HTTP CLIENT CONFIGURATION --- * Hostname was NOT found in DNS cache * Trying 192.168.6.25... * Connected to 192.168.6.25 (192.168.6.25) port 7547 (#0) > POST / HTTP/1.1 Host: 192.168.6.25:7547 Accept: */* User-Agent: easycwmp Content-Type: text/xml Content-Length: 3177 Expect: 100-continue < HTTP/1.1 100 Continue * Empty reply from server * Connection #0 to host 192.168.6.25 left intact rpc_inform(214): sending Inform http message failed I can see in the log that ubus initialization fails. I tried invoking the command: 'ubus list' but just get a "Failed to connect to ubus" reply. I've searched online, but have found no way to debug this. Thinking that this machine might have some out of date patches on it, I set up a new Linux VM using Mint 17, and installed everything fresh, but get the exact same result. Please let me know if there are any steps I can take to debug this. Does ubusd log anywhere? I can see messages from easycwmp in syslog, but nothing for ubus. | ||||
| Tags | No tags attached. | ||||
| e-mail notification | |||||
|
|
In fact ubus is used for notification. so the ubus fail has no relation with your problem. let's start with your problem and then see the ubus fail problem For the acs connection problem. it seems that your acs send an empty message after receiving the inform message instead of sending InformResponse. Could you provide the traffic capture (wireshark). |
|
|
Due to the loss of use from the machine I was using, I reinstalled easycwmp on a new linux machine. I no longer get the ubus errors, but on startup with the '-f -b' options, I get: config_init_local(53):: easycwmp.@local[0].interface=eth0 config_init_local(63):: easycwmp.@local[0].port=7547 config_init_local(81):: easycwmp.@local[0].ubus_socket=/var/run/ubus.sock config_init_local(69):: easycwmp.@local[0].username=pico config_init_local(75):: easycwmp.@local[0].password=pico config_init_acs(147):: easycwmp.@acs[0].scheme=http config_init_acs(153):: easycwmp.@acs[0].username=pico config_init_acs(159):: easycwmp.@acs[0].password=Pico2014 config_init_acs(165):: easycwmp.@acs[0].hostname=primehometrial.cisco.com config_init_acs(175):: easycwmp.@acs[0].port=8080 config_init_acs(181):: easycwmp.@acs[0].path=/dps/TR069 config_init_acs(187):: easycwmp.@acs[0].periodic_enable=1 config_init_acs(193):: easycwmp.@acs[0].periodic_interval=100 /usr/sbin/easycwmp: 34: export: Illegal option -n I'm assuming the '-n' is in one of the scripts somewhere? Any good way to track that down? |
|
|
I also have similar problem that test on linux of ARMv5TEJ platform, root # /usr/sbin/easycwmpd -f -b The error message output as below : config_init_local(53):: easycwmp.@local[0].interface=eth0 config_init_local(63):: easycwmp.@local[0].port=7547 config_init_local(81):: easycwmp.@local[0].ubus_socket=/tmp/ubus.sock config_init_acs(147):: easycwmp.@acs[0].scheme=http config_init_acs(153):: easycwmp.@acs[0].username=openacs config_init_acs(159):: easycwmp.@acs[0].password=openacs config_init_acs(165):: easycwmp.@acs[0].hostname=192.168.0.97 config_init_acs(175):: easycwmp.@acs[0].port=8080 config_init_acs(181):: easycwmp.@acs[0].path=/openacs/acs config_init_acs(187):: easycwmp.@acs[0].periodic_enable=1 config_init_acs(193):: easycwmp.@acs[0].periodic_interval=60 /usr/sbin/easycwmp: export: line 208: illegal option -n |
|
|
as indicted in the install page of easycwmp.org, you have to execute the following command after the install of easycwmp sudo ln -sf bash /bin/sh check that /bin/sh is linked to bash : user@jupiter /opt/dev/easycwmp $ ls -l /bin/sh lrwxrwxrwx 1 root root 4 7 201 /bin/sh -> dash user@jupiter /opt/dev/easycwmp $ sudo ln -sf bash /bin/sh user@jupiter /opt/dev/easycwmp $ ls -l /bin/sh lrwxrwxrwx 1 root root 4 1 15:22 /bin/sh -> bash |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-08-26 20:41 | thejimi | New Issue | |
| 2014-08-27 10:14 | mohamed.kallel | Note Added: 0000034 | |
| 2014-08-27 10:15 | mohamed.kallel | Note Edited: 0000034 | |
| 2014-09-15 20:00 | thejimi | Note Added: 0000037 | |
| 2014-09-23 10:53 | mohamed.kallel | Severity | block => minor |
| 2014-10-01 09:56 | janmus | Note Added: 0000059 | |
| 2014-10-01 16:30 |
|
Note Added: 0000060 | |
| 2014-10-01 17:03 |
|
Status | new => resolved |
| 2014-10-01 17:03 |
|
Resolution | open => fixed |
| 2014-10-01 17:03 |
|
Assigned To | => user13 |
