Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error "list index out of range" when running wibed-node script #10

Open
zavalyshyn opened this issue Sep 3, 2015 · 2 comments
Open
Labels

Comments

@zavalyshyn
Copy link
Contributor

For some unknown reason (yet) after resetting the node we may end up having ResultAck value but no CommandAck in /etc/config/wibed.

This causes confusion on server side when running wibed-node script. Here is an example of wibed-node output:

root@wibed-faaf86:~# wibed-node
---------------------------------------
Thu Sep  3 15:06:09 UTC 2015
---------------------------------------
API URL: http://wibed.ac.upc.edu/
Id: wibed-faaf86
Status: 1
Model: tl-wdr4300

Version: 7dbba9de
Experiment Id: 0000
Command Ack: None
Result Ack: 5
Flash is the overlay

Request:
{
 "status":1
}

Communication with server successful

{
 "errors": [
   "list index out of range"
 ], 
 "experiment": {
   "action": "PREPARE", 
   "id": 7, 
   "overlay": "ap_test7.tar.gz"
 }
}
Error sent by server:
1   list index out of range
root@wibed-faaf86:~# 
@emmdim
Copy link
Contributor

emmdim commented Sep 3, 2015

This may be a result of the wibed-reset script when a node is reinitializing. Maybe a uci commit command in missing after this line:
https://github.com/battlemesh/wibed-packages/blob/master/wibed-system/files/usr/sbin/wibed-reset#L44
as also in other parts of the script.

The inconsistency is possibly created when the db of the controller is deleted.

@emmdim emmdim added the bug label Sep 3, 2015
@emmdim
Copy link
Contributor

emmdim commented Sep 3, 2015

From the server side this issue is traced in this DB request:
https://redmine.confine-project.eu/projects/wibed-controller/repository/revisions/master/entry/blueprints/nodeapi/nodeapi.py#L194
where there are no expCommands.

p4u added a commit that referenced this issue May 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants