AIVA (A.I. Virtual Assistant): General-purpose virtual assistant for developers.
Home Page: http://kengz.me/aiva/
License: MIT License
Hi,
maybe you can provide a setup script depending on the chosen adapter...
i try those step without success:
ROCKETCHAT_ROOM=''
LISTEN_ON_ALL_PUBLIC=true
ROCKETCHAT_USER=bot
ROCKETCHAT_PASSWORD=bot
to: bin/.env-aiva
i can't test your new one yet, nevertheless the Jarvis bot works.
Let me know if you have successfully integrate it with hubot...
Thanks for your great work, kind regards,
YaRi
I ran 'npm run setup --debug' on my Dell and, like many others here, it would exit as "clients" would fail to join in time and then hang. Increasing the timeout in src/start-io.js to 150000 ms also didn't help, so I reduced the client count to a custom 2. It doesn't throw errors, but it still hangs. Any help?
Present on my system (ubuntu trusty) installed following all available documentation.
Also verified as an issue as same thing happens here: https://tonicdev.com/npm/jarvis-bot
I haven't yet found the construct or docs for what is needed in run.js in this particular package.
Any suggestions?
Fresh install on Ubuntu 16.04 keeps failing. Logs are empty.
Any suggestion would be greatly appreciated. I'm at a loss for what my error could be.
[email protected] setup /home/prisoner/aiva
bin/setup
Nodejs is already installed
Python3 is already installed
Reading package lists... Done
Building dependency tree
Reading state information... Done
postgresql is already the newest version (9.5+173).
postgresql-contrib is already the newest version (9.5+173).
The following packages were automatically installed and are no longer required:
libio-string-perl libtimedate-perl
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Postgresql is already started
Pip modules already installed
Npm modules already installed
[Wed Nov 02 2016 09:43:14 GMT-0700 (PDT)] INFO Authenticated database successfully
Sequelize [Node: 6.9.1, CLI: 2.4.0, ORM: 3.24.6]
Loaded configuration file "config/db.json".
Using environment "development".
No migrations were executed, database schema was already up to date.
Sequelize [Node: 6.9.1, CLI: 2.4.0, ORM: 3.24.6]
Loaded configuration file "config/db.json".
Using environment "test".
No migrations were executed, database schema was already up to date.
Sequelize [Node: 6.9.1, CLI: 2.4.0, ORM: 3.24.6]
Loaded configuration file "config/db.json".
Using environment "production".
No migrations were executed, database schema was already up to date.
prisoner@ubuntu:~/aiva$ npm start --debug
[email protected] start /home/prisoner/aiva
bin/start
[ ------- Starting on local machine, not Docker ------- ]
[email protected] development /home/prisoner/aiva
mkdir -p ./logs; NODE_ENV=development ./node_modules/forever/bin/forever --minUptime=1000 --spinSleepTime=1000 --killSignal=SIGTERM --uid aiva-development -m 10 -a index.js | tee ./logs/aiva-development.log
[Wed Nov 02 2016 09:45:16 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #1
[Wed Nov 02 2016 09:45:17 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #2
[Wed Nov 02 2016 09:45:19 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #3
[Wed Nov 02 2016 09:45:20 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #4
[Wed Nov 02 2016 09:45:21 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #5
[Wed Nov 02 2016 09:45:22 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #6
[Wed Nov 02 2016 09:45:23 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #7
[Wed Nov 02 2016 09:45:24 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #8
[Wed Nov 02 2016 09:45:26 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #9
[Wed Nov 02 2016 09:45:27 GMT-0700 (PDT)] ERROR
error: Forever detected script exited with code: 0
Hello,
I proceed with the all steps from the README.md for install AIVA. So, I actualized MariaDB to 10.1, follow the advice give from install processes. After try to run the program show me this:
[Wed Jun 20 2018 16:05:10 GMT+0000 (utc)] ERROR Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
Unhandled rejection Error: Command failed: ./node_modules/.bin/sequelize db:migrate --env development
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
From previous event:
at ConnectionManager.migrateDb (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/db.js:50:10)
From previous event:
at Promise.then (/home/marco/Projects/artificial_intelligence/AIVA/aiva/node_modules/sequelize/lib/promise.js:21:17)
at Object.start (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/aiva.js:52:6)
at Object. (/home/marco/Projects/artificial_intelligence/AIVA/aiva/index.js:4:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
error: Forever detected script exited with code: 0
error: Script restart attempt #3
[Wed Jun 20 2018 16:05:12 GMT+0000 (utc)] ERROR {
"0": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"1": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"2": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"length": 3
}
[Wed Jun 20 2018 16:05:13 GMT+0000 (utc)] ERROR Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
Unhandled rejection Error: Command failed: ./node_modules/.bin/sequelize db:migrate --env development
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
From previous event:
at ConnectionManager.migrateDb (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/db.js:50:10)
From previous event:
at Promise.then (/home/marco/Projects/artificial_intelligence/AIVA/aiva/node_modules/sequelize/lib/promise.js:21:17)
at Object.start (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/aiva.js:52:6)
at Object. (/home/marco/Projects/artificial_intelligence/AIVA/aiva/index.js:4:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
error: Forever detected script exited with code: 0
error: Script restart attempt #4
[Wed Jun 20 2018 16:05:15 GMT+0000 (utc)] ERROR {
"0": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"1": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"2": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"length": 3
}
[Wed Jun 20 2018 16:05:16 GMT+0000 (utc)] ERROR Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
Unhandled rejection Error: Command failed: ./node_modules/.bin/sequelize db:migrate --env development
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Socket.stream.socket.on (internal/child_process.js:346:11)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at Pipe._handle.close [as _onclose] (net.js:557:12)
From previous event:
at ConnectionManager.migrateDb (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/db.js:50:10)
From previous event:
at Promise.then (/home/marco/Projects/artificial_intelligence/AIVA/aiva/node_modules/sequelize/lib/promise.js:21:17)
at Object.start (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/aiva.js:52:6)
at Object. (/home/marco/Projects/artificial_intelligence/AIVA/aiva/index.js:4:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
error: Forever detected script exited with code: 0
error: Script restart attempt #5
[Wed Jun 20 2018 16:05:17 GMT+0000 (utc)] ERROR {
"0": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"1": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"2": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"length": 3
}
[Wed Jun 20 2018 16:05:19 GMT+0000 (utc)] ERROR Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
Unhandled rejection Error: Command failed: ./node_modules/.bin/sequelize db:migrate --env development
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
From previous event:
at ConnectionManager.migrateDb (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/db.js:50:10)
From previous event:
at Promise.then (/home/marco/Projects/artificial_intelligence/AIVA/aiva/node_modules/sequelize/lib/promise.js:21:17)
at Object.start (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/aiva.js:52:6)
at Object. (/home/marco/Projects/artificial_intelligence/AIVA/aiva/index.js:4:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
error: Forever detected script exited with code: 0
error: Script restart attempt #6
[Wed Jun 20 2018 16:05:21 GMT+0000 (utc)] ERROR {
"0": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"1": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"2": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"length": 3
}
[Wed Jun 20 2018 16:05:22 GMT+0000 (utc)] ERROR Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
Unhandled rejection Error: Command failed: ./node_modules/.bin/sequelize db:migrate --env development
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
From previous event:
at ConnectionManager.migrateDb (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/db.js:50:10)
From previous event:
at Promise.then (/home/marco/Projects/artificial_intelligence/AIVA/aiva/node_modules/sequelize/lib/promise.js:21:17)
at Object.start (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/aiva.js:52:6)
at Object. (/home/marco/Projects/artificial_intelligence/AIVA/aiva/index.js:4:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
error: Forever detected script exited with code: 0
error: Script restart attempt #7
[Wed Jun 20 2018 16:05:23 GMT+0000 (utc)] ERROR {
"0": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"1": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"2": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"length": 3
}
[Wed Jun 20 2018 16:05:25 GMT+0000 (utc)] ERROR Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
Unhandled rejection Error: Command failed: ./node_modules/.bin/sequelize db:migrate --env development
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
From previous event:
at ConnectionManager.migrateDb (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/db.js:50:10)
From previous event:
at Promise.then (/home/marco/Projects/artificial_intelligence/AIVA/aiva/node_modules/sequelize/lib/promise.js:21:17)
at Object.start (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/aiva.js:52:6)
at Object. (/home/marco/Projects/artificial_intelligence/AIVA/aiva/index.js:4:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
error: Forever detected script exited with code: 0
error: Script restart attempt #8
[Wed Jun 20 2018 16:05:26 GMT+0000 (utc)] ERROR {
"0": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"1": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"2": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"length": 3
}
[Wed Jun 20 2018 16:05:28 GMT+0000 (utc)] ERROR Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
Unhandled rejection Error: Command failed: ./node_modules/.bin/sequelize db:migrate --env development
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
From previous event:
at ConnectionManager.migrateDb (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/db.js:50:10)
From previous event:
at Promise.then (/home/marco/Projects/artificial_intelligence/AIVA/aiva/node_modules/sequelize/lib/promise.js:21:17)
at Object.start (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/aiva.js:52:6)
at Object. (/home/marco/Projects/artificial_intelligence/AIVA/aiva/index.js:4:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
error: Forever detected script exited with code: 0
error: Script restart attempt #9
[Wed Jun 20 2018 16:05:30 GMT+0000 (utc)] ERROR {
"0": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"1": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"2": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MariaDB client",
"sqlState": "08004",
"fatal": true
}
},
"length": 3
}
[Wed Jun 20 2018 16:05:31 GMT+0000 (utc)] ERROR Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
Unhandled rejection Error: Command failed: ./node_modules/.bin/sequelize db:migrate --env development
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client
at ChildProcess.exithandler (child_process.js:275:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
From previous event:
at ConnectionManager.migrateDb (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/db.js:50:10)
From previous event:
at Promise.then (/home/marco/Projects/artificial_intelligence/AIVA/aiva/node_modules/sequelize/lib/promise.js:21:17)
at Object.start (/home/marco/Projects/artificial_intelligence/AIVA/aiva/src/aiva.js:52:6)
at Object. (/home/marco/Projects/artificial_intelligence/AIVA/aiva/index.js:4:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
error: Forever detected script exited with code: 0
Any possible solution?
Thank you for your effort and project and Kind regards,
Marco Baturan.
I have the Latest versions of everything on Ubuntu 17.04. npm and node.js are latest as well. mySQL is installed, latest version. New Ubuntu 17.04 build. Clean machine.
npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'run', 'setup' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'presetup', 'setup', 'postsetup' ]
5 info lifecycle [email protected]presetup: [email protected]presetup: no script for presetup, continuing
6 silly lifecycle [email protected]
7 info lifecycle [email protected]setup: [email protected]setup: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]setup: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/mario/git/aiva/node_modules/.bin:/home/mario/anaconda3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/binsetup: CWD: /home/mario/git/aiva
10 verbose lifecycle [email protected]
11 silly lifecycle [email protected]setup: Args: [ '-c', 'bin/setup' ]setup: Returned: code: 1 signal: null
12 silly lifecycle [email protected]
13 info lifecycle [email protected]~setup: Failed to exec setup script
14 verbose stack Error: [email protected] setup: bin/setup
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:891:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/mario/git/aiva
17 error Linux 4.10.0-32-generic
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "setup"
19 error node v6.11.2
20 error npm v3.10.10
21 error code ELIFECYCLE
22 error [email protected] setup: bin/setup
22 error Exit status 1
23 error Failed at the [email protected] setup script 'bin/setup'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the aiva package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error bin/setup
23 error You can get information on how to open an issue for this project with:
23 error npm bugs aiva
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls aiva
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
The README mentions using a script at bin/install on line 64 but I don't see that file in the project. Is that an outdated reference?
Hi first of all very nice approach to deduce the machine response. I was trying your https://explosion.ai/blog/chatbot-node-js-spacy tutorial but i can't see any data getting saved in Graph Db i am using Slack as the chat client. I am getting something like below on the terminal but no data seems get saved in Neo4j,
[Wed Apr 12 2017 19:06:50 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:06:50 GMT+0000 (UTC)] DEBUG hasher.handle invoking cb for global-client
[Wed Apr 12 2017 19:06:50 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:06:50 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:06:50 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:06:50 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:06:50 GMT+0000 (UTC)] ERROR
[Wed Apr 12 2017 19:06:50 GMT+0000 (UTC)] INFO Knowledge saved to brain
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG [In log]: alice hello_py py
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG Started global js socketIO client for SLACK at 6466
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG Added a callback to hasher for global-client
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] INFO global-client-js 7l4lt02SGuYEtjo7AAAC joined, -5 remains
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] INFO All 4 IO clients have joined
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG IO on pass, msg: {
"hash": "global-client-js_d71ff935b97c97237e8618234aac84b7",
"from": "global-client-js",
"input": "hello_py py",
"to": "nlp.cgkb-py",
"intent": "parse"
} fn: undefined
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG IO on pass, msg: {
"to": "global-client-js",
"from": "cgkb-py",
"hash": "global-client-js_d71ff935b97c97237e8618234aac84b7",
"output": null
} fn: undefined
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG Added a callback to hasher for global-client
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG IO on pass, msg: {
"hash": "global-client-js_c9d8d43bf56a7f451e47587bdc08bd43",
"from": "global-client-js",
"input": "hello_py py",
"to": "convo_classifier.py",
"intent": "classify"
} fn: undefined
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG hasher.handle invoking cb for global-client
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] DEBUG hash string exists for global-client
[Wed Apr 12 2017 19:08:19 GMT+0000 (UTC)] INFO Knowledge saved to brain
Below is my config json and my Neo4j is working on 7474 with Neo4j/0000 credentials
"PORTS": { "NEO4J": 7476, "SOCKETIO": 6466, "SLACK": 8345, "TELEGRAM": 8443, "FB": 8545 },
can you please guide me through.
Hi,
I have installed as per the blog (https://explosion.ai/blog/chatbot-node-js-spacy). and I get following error. I am exploring to use spacy, aiva, and spacy-nlpfor building our chatbots. During evaluation I am stuck as given below.
guru@qubeme:~/qubeme/aiva$ npm start --debug
[email protected] start /home/guru/qubeme/aiva
bin/start
[ ------- Starting on local machine, not Docker ------- ]
[email protected] development /home/guru/qubeme/aiva
mkdir -p ./logs; NODE_ENV=development ./node_modules/forever/bin/forever --minUptime=1000 --spinSleepTime=1000 --killSignal=SIGTERM --uid aiva-development -m 10 -a index.js | tee ./logs/aiva-development.log
[Sun Nov 06 2016 21:39:39 GMT+0000 (utc)] INFO Authenticated database successfully
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] DEBUG
Sequelize [Node: 6.9.1, CLI: 2.4.0, ORM: 3.24.8]
Loaded configuration file "config/db.json".
Using environment "development".
No migrations were executed, database schema was already up to date.
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] INFO Starting aiva process
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] DEBUG globalConfig {
"BOTNAME": "aivadev",
"PORTS": {
"NEO4J": 7476,
"SOCKETIO": 6466,
"SLACK": 8345,
"TELEGRAM": 8443,
"FB": 8545
},
"NGROK_AUTH": "sign up at https://ngrok.com for custom domain",
"ADMINS": [
"[email protected]"
],
"TEST": {
"HUBOT_SHELL_USER_ID": "ID0000001",
"HUBOT_SHELL_USER_NAME": "alice"
}
}
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] INFO Starting poly-socketio server on port: 6466, expecting 4 IO clients
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] DEBUG adapterConfig {
"ACTIVATE": true,
"HUBOT_SLACK_TOKEN": "xoxb-101071100564-BfpiYk5RUTVvmhLgqRYif8zi"
}
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] DEBUG import js lib from client.js
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] INFO Starting socketIO client for js at 6466
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] INFO Starting socketIO client for python3 at 6466
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] DEBUG Set SLACK PORT: 8345
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] DEBUG No WEBHOOK set for adapter SLACK
[Sun Nov 06 2016 21:39:42 GMT+0000 (utc)] INFO Deploying bot aivadev with adapter SLACK
[Sun Nov 06 2016 21:39:43 GMT+0000 (utc)] INFO Starting socketIO client for python3 at 6466
[Sun Nov 06 2016 21:39:47 GMT+0000 (utc)] DEBUG js 7kXQcLv692VVYP2HAAAA joined, 3 remains
[Sun Nov 06 2016 21:39:48 GMT+0000 (utc)] DEBUG py GymNT7B3Z70qe52NAAAB joined, 2 remains
[Sun Nov 06 2016 21:39:48 GMT+0000 (utc)] DEBUG cgkb-py SDAEbR5_vH1kVGvWAAAC joined, 1 remains
[Sun Nov 06 2016 21:39:48 GMT+0000 (utc)] INFO Logged in as qubemefaq of ETIOS
[Sun Nov 06 2016 21:39:48 GMT+0000 (utc)] INFO Slack client now connected
[Sun Nov 06 2016 21:39:49 GMT+0000 (utc)] DEBUG Started global js socketIO client for SLACK at 6466
[Sun Nov 06 2016 21:39:49 GMT+0000 (utc)] DEBUG global-client-js cxDW7rY6y7mPZz29AAAD joined, 0 remains
[Sun Nov 06 2016 21:39:49 GMT+0000 (utc)] INFO All 4 IO clients have joined
[Sun Nov 06 2016 21:40:02 GMT+0000 (utc)] DEBUG Started global js socketIO client for SLACK at 6466
[Sun Nov 06 2016 21:40:02 GMT+0000 (utc)] DEBUG Added a callback to hasher for global-client
[Sun Nov 06 2016 21:40:03 GMT+0000 (utc)] DEBUG global-client-js cxDW7rY6y7mPZz29AAAD joined, -1 remains
[Sun Nov 06 2016 21:40:03 GMT+0000 (utc)] INFO All 4 IO clients have joined
[Sun Nov 06 2016 21:40:03 GMT+0000 (utc)] DEBUG IO on pass, msg: {
"hash": "global-client-js_ca2ac79176604b19bfdb2fcb29e75584",
"from": "global-client-js",
"input": "Book a flight from new york to london for sunday.",
"to": "nlp.cgkb-py",
"intent": "parse"
} fn: undefined
[Sun Nov 06 2016 21:40:03 GMT+0000 (utc)] DEBUG IO on pass, msg: {
"to": "global-client-js",
"output": null,
"from": "cgkb-py",
"hash": "global-client-js_ca2ac79176604b19bfdb2fcb29e75584"
} fn: undefined
[Sun Nov 06 2016 21:40:03 GMT+0000 (utc)] DEBUG hash string exists for global-client
[Sun Nov 06 2016 21:40:03 GMT+0000 (utc)] DEBUG hasher.handle invoking cb for global-client
[Sun Nov 06 2016 21:40:03 GMT+0000 (utc)] DEBUG hash string exists for global-client
[Sun Nov 06 2016 21:40:03 GMT+0000 (utc)] DEBUG hasher.handle invoking cb for global-client
Unhandled rejection ReferenceError: qp is not defined
at Object. (/home/guru/qubeme/aiva/node_modules/cgkb/src/cgkb.js:50:34)
at undefined.next (native)
at onFulfilled (/home/guru/qubeme/aiva/node_modules/co/index.js:65:19)
at runCallback (timers.js:637:20)
at tryOnImmediate (timers.js:610:5)
at processImmediate [as _immediateCallback] (timers.js:582:5)
From previous event:
at Object.co (/home/guru/qubeme/aiva/node_modules/co/index.js:50:10)
at Object.createPromise [as add] (/home/guru/qubeme/aiva/node_modules/co/index.js:30:15)
at TextListener.robot.respond [as callback] (/home/guru/qubeme/aiva/scripts/cgkb-demo.js:29:12)
at /home/guru/qubeme/aiva/node_modules/hubot/src/listener.coffee:65:12
at allDone (/home/guru/qubeme/aiva/node_modules/hubot/src/middleware.coffee:44:37)
at /home/guru/qubeme/aiva/node_modules/hubot/node_modules/async/lib/async.js:274:13
at Object.async.eachSeries (/home/guru/qubeme/aiva/node_modules/hubot/node_modules/async/lib/async.js:142:20)
at Object.async.reduce (/home/guru/qubeme/aiva/node_modules/hubot/node_modules/async/lib/async.js:268:15)
at /home/guru/qubeme/aiva/node_modules/hubot/src/middleware.coffee:49:13
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
^C
Hi,
I have started AIVA as root user. After few days when I am trying to start aiva as normal user in my linux machine, it is not able to load all components. Please find below trace,
[email protected] start /data/installations/aiva/aiva-ISE/aiva
bin/start
[ ------- Starting on local machine, not Docker ------- ]
[email protected] development /data/installations/aiva/aiva-ISE/aiva
mkdir -p ./logs; NODE_ENV=development ./node_modules/forever/bin/forever --minUptime=1000 --spinSleepTime=1000 --killSignal=SIGTERM --uid aiva-ice-development -m 10 -a index.js | tee ./logs/aiva-ice-development.log
[Thu Aug 23 2018 08:19:39 GMT+0000 (utc)] INFO Authenticated database successfully
[Thu Aug 23 2018 08:19:40 GMT+0000 (utc)] INFO Starting aiva process
[Thu Aug 23 2018 08:19:40 GMT+0000 (utc)] INFO Starting poly-socketio server on port: 6466, expecting 4 IO clients
[Thu Aug 23 2018 08:19:40 GMT+0000 (utc)] INFO Starting socketIO client for js at 6466
[Thu Aug 23 2018 08:19:40 GMT+0000 (utc)] INFO Starting socketIO client for python at 6466
[Thu Aug 23 2018 08:19:40 GMT+0000 (utc)] INFO Deploying bot aiva-ice with adapter HTTPADAPTER
[Thu Aug 23 2018 08:19:40 GMT+0000 (utc)] INFO Starting socketIO client for python at 6466
[Thu Aug 23 2018 08:19:40 GMT+0000 (utc)] ERROR Traceback (most recent call last):
File "/data/installations/aiva/aiva-ISE/aiva/lib/client.py", line 10, in
import six
ImportError: No module named six
[Thu Aug 23 2018 08:19:40 GMT+0000 (utc)] ERROR Traceback (most recent call last):
File "/data/installations/aiva/aiva-ISE/aiva/node_modules/spacy-nlp/src/client.py", line 10, in
import six
ImportError: No module named six
Hi,
When I ran this command "npm run setup", I got 'bin' is not recognized as an internal or external command, operable program or batch file.
Any suggestion? (You can see my command line in the following).
HI,
Why is the mitsuku-api removed from the repo?
How are the default chat commands handled in the current implementation?
Thanks & Regards
C:\xampp\htdocs\aiva>npm run setup
[email protected] setup C:\xampp\htdocs\aiva
bin/setup
'bin' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] setup: bin/setup
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] setup script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\zen education\AppData\Roaming\npm-cache_logs\2018-05-13T14_50_24_755Z-debug.log
I tried both Docker and non-Docker setup, and in both cases, when I get to the npm start --debug step, I get
[Tue Oct 25 2016 21:49:24 GMT+0000 (UTC)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #1until forever reaches its max number of attempts. Can't really figure out where it is having trouble.
I'd love to get this up and running, do you have any ideas?
Neo4j Isn't available now and the setup file installs it and we cannot run apt-get update after that please help
I ran through the tutorial, and things work for simple commands (ping, for instance), but parsing is not working. When it's running, I see this failure:
[Fri Nov 11 2016 23:32:36 GMT+0000 (UTC)] DEBUG IO on pass, msg: {
"hash": "global-client-js_dd811cf6fe0efa148f76b0df27a5c37b",
"from": "global-client-js",
"input": "test",
"to": "nlp.cgkb-py",
"intent": "parse"
} fn: undefined
Unhandled rejection TimeoutError: operation timed out
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5)
From previous event:
at cdefer (/Users/patwhite/Source/Temp/aiva2/node_modules/poly-socketio/src/global-client.js:93:6)
at Socket.pass (/Users/patwhite/Source/Temp/aiva2/node_modules/poly-socketio/src/global-client.js:36:15)
at Object.parse (/Users/patwhite/Source/Temp/aiva2/node_modules/spacy-nlp/src/nlp.js:16:24)
at Object. (/Users/patwhite/Source/Temp/aiva2/node_modules/cgkb/src/cgkb.js:44:27)
at undefined.next (native)
at onFulfilled (/Users/patwhite/Source/Temp/aiva2/node_modules/co/index.js:65:19)
at /Users/patwhite/Source/Temp/aiva2/node_modules/co/index.js:54:5
From previous event:
at Object.co (/Users/patwhite/Source/Temp/aiva2/node_modules/co/index.js:50:10)
at Object.createPromise [as add] (/Users/patwhite/Source/Temp/aiva2/node_modules/co/index.js:30:15)
at TextListener.robot.respond [as callback] (/Users/patwhite/Source/Temp/aiva2/scripts/cgkb-demo.js:29:12)
at /Users/patwhite/Source/Temp/aiva2/node_modules/hubot/src/listener.coffee:65:12
at allDone (/Users/patwhite/Source/Temp/aiva2/node_modules/hubot/src/middleware.coffee:44:37)
at /Users/patwhite/Source/Temp/aiva2/node_modules/hubot/node_modules/async/lib/async.js:274:13
at Object.async.eachSeries (/Users/patwhite/Source/Temp/aiva2/node_modules/hubot/node_modules/async/lib/async.js:142:20)
at Object.async.reduce (/Users/patwhite/Source/Temp/aiva2/node_modules/hubot/node_modules/async/lib/async.js:268:15)
at /Users/patwhite/Source/Temp/aiva2/node_modules/hubot/src/middleware.coffee:49:13
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
I can use spacy separately for NLP, but maybe it's an issue with the socket io bridge?
I followed the tutorial directly, this is on Mac El Capitan, node 6.9.1, python 3.5.1.
I have one question about slack
If I add my slackbot to channel, it won't reply me.
But when I send message to slackbot directly. it works!
How can I fix it?
If I use slack adapter it can work in both channel and slackbot.
Please help me thanks :-)
https://github.com/kengz/aiva/blob/master/bin/start#L18 looks like it still has the old mysql in there and will fail out.
As discussed in #28 (comment)
aiva is returning null as output:
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] INFO Receiving message_id: XXXX
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG Started global js socketIO client for TELEGRAM at 6466
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG Added a callback to hasher for global-client
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG global-client-js PyIHtjUvUqrZHnUUAAAD joined, -2 remains
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] INFO All 4 IO clients have joined
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG IO on pass, msg: {
"hash": "global-client-js_4ea7f9bc23a43715e7a10bec65876642",
"from": "global-client-js",
"input": "Hello there",
"to": "nlp.cgkb-py",
"intent": "parse"
} fn: undefined
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG IO on pass, msg: {
"from": "cgkb-py",
"output": null,
"hash": "global-client-js_4ea7f9bc23a43715e7a10bec65876642",
"to": "global-client-js"
} fn: undefined
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG hash string exists for global-client
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG hasher.handle invoking cb for global-client
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG hash string exists for global-client
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG hasher.handle invoking cb for global-client
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG hash string exists for global-client
[Tue Nov 08 2016 13:24:25 GMT+0000 (utc)] DEBUG hasher.handle invoking cb for global-client
[Tue Nov 08 2016 13:24:26 GMT+0000 (utc)] INFO Sending message to room: XXXXXXXNode.js: 6.9.1
OS:
Distributor ID: Debian
Description: Debian GNU/Linux 8.6 (jessie)
Release: 8.6
Codename: jessie
pip list shows:
cloudpickle (0.2.1)
cymem (1.31.2)
Cython (0.25.1)
murmurhash (0.26.4)
numpy (1.11.2)
pathlib (1.0.1)
pip (9.0.1)
plac (0.9.6)
preshed (0.46.4)
requests (2.11.1)
semver (2.7.1)
setuptools (28.8.0)
six (1.10.0)
socketIO-client (0.7.0)
spacy (1.2.0)
sputnik (0.9.3)
thinc (5.0.8)
ujson (1.35)
virtualenv (1.11.6)
websocket-client (0.37.0)
wheel (0.29.0)
@kengz could you point me on how to know with which version of python spacy was installed, I have both:
$ python3 --version
Python 3.4.2
$ python --version
Python 2.7.9
Still awaiting for author to merge, test, publish the new hubot-fb with auto-setup for Fb webhook. In the mean time, after you've installed the npm package, replace node_modules/hubot-fb/src/fb.coffee with the following script:
try
{Robot,Adapter,TextMessage,User} = require 'hubot'
catch
prequire = require('parent-require')
{Robot,Adapter,TextMessage,User} = prequire 'hubot'
Mime = require 'mime'
inspect = require('util').inspect
class FBMessenger extends Adapter
constructor: ->
super
@page_id = process.env['FB_PAGE_ID']
@app_id = process.env['FB_APP_ID']
@app_secret = process.env['FB_APP_SECRET']
@token = process.env['FB_PAGE_TOKEN']
@vtoken = process.env['FB_VERIFY_TOKEN'] or 'hubotfbverification'
@routeURL = process.env['FB_ROUTE_URL'] or '/fb'
@webhookURL = process.env['FB_WEBHOOK'] + @routeURL
_sendImages = process.env['FB_SEND_IMAGES']
if _sendImages is undefined
@sendImages = true
else
@sendImages = _sendImages is 'true'
@apiURL = 'https://graph.facebook.com/v2.6'
@pageURL = @apiURL + '/'+ @page_id
@messageEndpoint = @pageURL + '/messages?access_token=' + @token
@subscriptionEndpoint = @pageURL + '/subscribed_apps?access_token=' + @token
@userProfileEndpoint = @pageURL + '/subscribed_apps?access_token=' + @token
@appAccessTokenEndpoint = 'https://graph.facebook.com/oauth/access_token?client_id=' + @app_id + '&client_secret=' + @app_secret + '&grant_type=client_credentials'
@setWebhookEndpoint = @pageURL + '/subscriptions'
@msg_maxlength = 320
send: (envelope, strings...) ->
@_sendText envelope.user.id, msg for msg in strings
if envelope.fb?.richMsg?
@_sendRich envelope.user.id, envelope.fb.richMsg
_sendText: (user, msg) ->
data = {
recipient: {id: user},
message: {}
}
if @sendImages
mime = Mime.lookup(msg)
if mime is "image/jpeg" or mime is "image/png" or mime is "image/gif"
data.message.attachment = { type: "image", payload: { url: msg }}
else
data.message.text = msg.substring(0,@msg_maxlength)
else
data.message.text = msg
@_sendAPI data
_sendRich: (user, richMsg) ->
data = {
recipient: {id: user},
message: richMsg
}
@_sendAPI data
_sendAPI: (data) ->
self = @
data = JSON.stringify(data)
@robot.http(@messageEndpoint)
.query({access_token:self.token})
.header('Content-Type', 'application/json')
.post(data) (error, response, body) ->
if error
self.robot.logger.error 'Error sending message: #{error}'
return
unless response.statusCode in [200, 201]
self.robot.logger.error "Send request returned status " +
"#{response.statusCode}. data='#{data}'"
self.robot.logger.error body
return
reply: (envelope, strings...) ->
@send envelope, strings
_receiveAPI: (event) ->
self = @
user = @robot.brain.data.users[event.sender.id]
unless user?
self.robot.logger.debug "User doesn't exist, creating"
@_getUser event.sender.id, event.recipient.id, (user) ->
self._dispatch event, user
else
self.robot.logger.debug "User exists"
self._dispatch event, user
_dispatch: (event, user) ->
envelope = {
event: event,
user: user,
room: event.recipient.id
}
if event.message?
@_processMessage event, envelope
else if event.postback?
@_processPostback event, envelope
else if event.delivery?
@_processDelivery event, envelope
_processMessage: (event, envelope) ->
@robot.logger.debug inspect event.message
if event.message.attachments?
envelope.attachments = event.message.attachments
@robot.emit "fb_richMsg", envelope
@_processAttachment event, envelope, attachment for attachment in envelope.attachments
if event.message.text?
text = @cleanMessageText event.message.text, envelope.room
msg = new TextMessage envelope.user, text, event.message.mid
@receive msg
@robot.logger.info "Reply message to room/message: " + envelope.user.name + "/" + event.message.mid
cleanMessageText: (text, chat_id) ->
# If it is a private chat, automatically prepend the bot name if it does not exist already.
if (chat_id > 0)
# Strip out the stuff we don't need.
text = text.replace(/^\//g, '').trim()
text = text.replace(new RegExp('^@?' + @robot.name.toLowerCase(), 'gi'), '');
text = text.replace(new RegExp('^@?' + @robot.alias.toLowerCase(), 'gi'), '') if @robot.alias
text = @robot.name + ' ' + text.trim()
else
text = text.trim()
return text
_processAttachment: (event, envelope, attachment) ->
unique_envelope = {
event: event,
user: envelope.user,
room: envelope.room,
attachment: attachment
}
@robot.emit "fb_richMsg_#{attachment.type}", unique_envelope
_processPostback: (event, envelope) ->
envelope.payload = event.postback.payload
@robot.emit "fb_postback", envelope
_processDelivery: (event, envelope) ->
@robot.emit "fb_delivery", envelope
_getUser: (userId, page, callback) ->
self = @
@robot.http(@apiURL + '/' + userId)
.query({fields:"first_name,last_name,profile_pic",access_token:self.token})
.get() (error, response, body) ->
if error
self.robot.logger.error 'Error getting user profile: #{error}'
return
unless response.statusCode is 200
self.robot.logger.error "Get user profile request returned status " +
"#{response.statusCode}. data='#{body}'"
self.robot.logger.error body
return
userData = JSON.parse body
userData.name = userData.first_name
userData.room = page
user = new User userId, userData
self.robot.brain.data.users[userId] = user
callback user
run: ->
self = @
unless @token
@emit 'error', new Error 'The environment variable "FB_PAGE_TOKEN" is required.'
unless @vtoken
@emit 'error', new Error 'The environment variable "FB_VERIFY_TOKEN" is required.'
unless @page_id
@emit 'error', new Error 'The environment variable "FB_PAGE_ID" is required.'
unless @app_id
@emit 'error', new Error 'The environment variable "FB_APP_ID" is required.'
unless @app_secret
@emit 'error', new Error 'The environment variable "FB_APP_SECRET" is required.'
unless process.env['FB_WEBHOOK']
@emit 'error', new Error 'The environment variable "FB_WEBHOOK" is required.'
@robot.http(@subscriptionEndpoint)
.query({access_token:self.token})
.post() (error, response, body) ->
self.robot.logger.info "subcribed app to page: " + body
@robot.router.get [@routeURL], (req, res) ->
if req.param('hub.mode') == 'subscribe' and req.param('hub.verify_token') == self.vtoken
res.send req.param('hub.challenge')
self.robot.logger.info "successful webhook verification"
else
res.send 400
@robot.router.post [@routeURL], (req, res) ->
@robot.logger.debug "Received payload: " + JSON.stringify(req.body)
messaging_events = req.body.entry[0].messaging
self._receiveAPI event for event in messaging_events
res.send 200
@robot.http(@appAccessTokenEndpoint)
.get() (error, response, body) ->
self.app_access_token = body.split("=").pop()
self.robot.http(self.setWebhookEndpoint)
.query(
object: 'page',
callback_url: self.webhookURL
fields: 'messaging_optins, messages, message_deliveries, messaging_postbacks'
verify_token: self.vtoken
access_token: self.app_access_token
)
.post() (error2, response2, body2) ->
self.robot.logger.info "FB webhook set/updated: " + body2
@robot.logger.info "FB-adapter initialized"
@emit "connected"
exports.use = (robot) ->
new FBMessenger robot
Running the line of code no longer download the spaCy's models, because there are now three different ones: en_core_web_sm, en_core_web_md, en_core_web_lg, en_vectors_web_lg.
Which one (if any) is the correct one to download during setup, and should the setup file be changed at line 125 in order to follow the change?
Hi trying to run it on mac and following the blog
My node version is 7
No error encountered during the setup run. aiva-development.log is empty.
[ ------- Starting on local machine, not Docker ------- ]
> [email protected] development /Users/rusty/codes/aiva
> mkdir -p ./logs; NODE_ENV=development ./node_modules/forever/bin/forever --minUptime=1000 --spinSleepTime=1000 --killSignal=SIGTERM --uid aiva-development -m 10 -a index.js | tee ./logs/aiva-development.log
[Tue Jan 24 2017 06:53:01 GMT+0000 (UTC)] ERROR
[Tue Jan 24 2017 06:53:01 GMT+0000 (UTC)] ERROR
error: Forever detected script exited with code: 0
error: Script restart attempt #1
Tried to follow steps by registering & installing ngrok and reading documentations of Hubot.
But still in vain when AIVA tries to setup web hook with Facebook
[Sat Jan 07 2017 15:49:23 GMT+0000 (UTC)] INFO FB-adapter initialized
[Sat Jan 07 2017 15:49:31 GMT+0000 (UTC)] ^[[32mINFO^[[39m global-client-js 1e3RZI4gNFgOjz8dAAAB joined, 2 remains
[Sat Jan 07 2017 15:49:31 GMT+0000 (UTC)] INFO subscribed app to page: {"success":true}
[Sat Jan 07 2017 15:49:32 GMT+0000 (UTC)] INFO FB webhook set/updated: {"error":{"message":"(#2200) Callback verification failed with the following errors: HTTP Status Code = 502; HTTP Message = Bad Gateway","type":"OAuthException","code":2200,"fbtrace_id":"D9B6\/qYRiGg"}}
My AIVA setup:
{
"BOTNAME": "aivadev",
"PORTS": {
"NEO4J": 7476,
"SOCKETIO": 6466,
"SLACK": 8345,
"TELEGRAM": 8443,
"FB": 8545
},
"NGROK_AUTH": "5Q45TLi2hCPk4nvWsxpHo_3mXYf4z7PjJqXXXXXXXX",
"ADMINS": ["[email protected]"],
"ACTIVATE_IO_CLIENTS": {
"ruby": false,
"python": true
},
"ADAPTERS": {
"SLACK": {
"ACTIVATE": false,
"HUBOT_SLACK_TOKEN": "add custom slack bot https://my.slack.com/services/new/bot"
},
"TELEGRAM": {
"ACTIVATE": false,
"TELEGRAM_TOKEN": "get from bot father https://core.telegram.org/bots#3-how-do-i-create-a-bot",
"BOTNAME": "your bot name from bot father",
"WEBHOOK_KEY": "TELEGRAM_WEBHOOK"
},
"FB": {
"ACTIVATE": true,
"FB_PAGE_ID": "254764828034XXX",
"FB_APP_ID": "948466065252XXX",
"FB_APP_SECRET": "e1c75419d1fcafb1967c92afXXXXXXXX",
"FB_PAGE_TOKEN": "EAANenZCbmojMBAHadI1dj6fZCGbEv2NEY5x0jAF6NLYOMtm9YIhmrvwGoYktc5BYlgL93aUQGdWb8R2td8xSoGF9C5ZAcjo22gbrAgaIjlimaZBS6jVAUPZAZAfbzVb6gxZCt2N6iFV3yLy6ZB6uqs7JtDfQXCgQqSdXXXXXXXXXXXXXXXX",
"FB_AUTOHEAR": true,
"WEBHOOK_KEY": "FB_WEBHOOK_BASE",
"FB_WEBHOOK_BASE": "optional: set a persistent webhook url if you have one on ngrok, since FB takes 10 mins to update it",
"FB_ROUTE_URL": "/fb"
}
},
"TEST": {
"HUBOT_SHELL_USER_ID": "ID0000001",
"HUBOT_SHELL_USER_NAME": "alice"
}
}
Could you tell me some more thorough steps to make it work?
Your domain may have been hijacked.
Hey
Ive been trying to setup the environment in kali linux and keeps showing error. Can anyone help me out with this?
Ive pasted the error below:
``Nodejs is already installed
Python3 is already installed
MySQL is already installed
MySQL is already started
Neo4j is already installed
Pip modules already installed
spaCy model:
/usr/bin/python3: No module named sputnik
/usr/bin/python: No module named spacy.en
Npm modules already installed
/home/hulkbuster/Documents/aiva/src/db.js:2
const { exec } = require('child_process')
^
SyntaxError: Unexpected token {
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:140:18)
at node.js:1043:3
Sequelize [Node: 4.8.4, CLI: 2.8.0, ORM: 3.30.4]
Loaded configuration file "config/db.json".
Using environment "development".
Unable to connect to database: SequelizeConnectionError: ER_BAD_DB_ERROR: Unknown database 'aiva_dev'
Sequelize [Node: 4.8.4, CLI: 2.8.0, ORM: 3.30.4]
Loaded configuration file "config/db.json".
Using environment "test".
Unable to connect to database: SequelizeConnectionError: ER_BAD_DB_ERROR: Unknown database 'aiva_test'
Sequelize [Node: 4.8.4, CLI: 2.8.0, ORM: 3.30.4]
Loaded configuration file "config/db.json".
Using environment "production".
Unable to connect to database: SequelizeConnectionError: ER_BAD_DB_ERROR: Unknown database 'aiva_prod'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] setup: bin/setup
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] setup script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2017-11-05T13_39_51_677Z-debug.log``
The documentation links to https://github.com/kengz/aiva/tree/master/docs/HTMI.md but the link is broken same for Context Aware Knowledge Graph
Getting TimeoutErros when calling most of the AI scripts.
Basic hubot scripts and simple message replies (i.e. messaging "titanic") work, but not the more complicated ones.
Running from the docker image using Slack adapter.
Unhandled rejection TimeoutError: operation timed out at tryOnTimeout (timers.js:224:11) at Timer.listOnTimeout (timers.js:198:5) From previous event: at cdefer (/opt/aiva/lib/client.js:167:6) at pass (/opt/aiva/lib/client.js:111:15) at TextListener.callback (/opt/aiva/scripts/translate.js:28:12) at /opt/aiva/node_modules/hubot/src/listener.coffee:65:12 at allDone (/opt/aiva/node_modules/hubot/src/middleware.coffee:44:37) at /opt/aiva/node_modules/hubot/node_modules/async/lib/async.js:274:13 at Object.async.eachSeries (/opt/aiva/node_modules/hubot/node_modules/async/lib/async.js:142:20) at Object.async.reduce (/opt/aiva/node_modules/hubot/node_modules/async/lib/async.js:268:15) at /opt/aiva/node_modules/hubot/src/middleware.coffee:49:13 at _combinedTickCallback (internal/process/next_tick.js:67:7) at process._tickCallback (internal/process/next_tick.js:98:9)
hi @kengz!
(hopefully I am not mistaken) it looks like client.py will fail to start and return an error as soon as any message is received, regardless of the type of message (warning, info, not necessarily errors).
Here is how I got to this conclusion:
dnn_titanic_train.py (actually all AI scripts too) from AIVA v3 and brought them over to my local clone of AIVA v4tensorflow with GPU support==> When starting the node app (npm start --debug), I get the following:
ERROR I tensorflow/stream_executor/dso_loader.cc:111] successfully opened CUDA library libcublas.so locally
This actually not an error message, when starting a python console and running import tensorflow, several messages telling me the successfully loaded cuda libs. I can also run the MNIST training example from TF, etc.
So, to double-check it wasn't caused by the GPU-TF version, I made another virtual env, this time with the CPU tensorflow version. Then I got warning messages from tensorflow:
ERROR <...>/cross_validation.py:44: DeprecationWarning: This module was deprecated in version 0.18 <...>, DeprecationWarning)
which I took care of by upgrading the dnn_titanic_train.py code so that it works on tensorflow v0.11RC1 (also DNNClassifier class has changed, etc.).
Then I got another tensorflow warning I couldn't get past:
ERROR WARNING:tensorflow:float64 is not supported by many models, consider casting to float32 which should be released in the official tensorflow v0.11 (link to issue).
In theory, to make it work, I would have to go back to tensorflow v0.9 or earlier (provided I don't encounter other warning messages). Also we can forget about the GPU tensorflow.
Bottomline, these messages are not error messages but are interpreted as such. Do you confirm this problem?
Thanks for your insight!
(btw, I'm on the cgkb branch but it shouldn't matter I think)
Why AIVA is consuming so much RAM, My computer hangs if i run command npm start ?
The bot seems not manipulating my messages. And here is the debug logs. What should I do?
[Sat Jan 07 2017 16:24:39 GMT+0000 (UTC)] DEBUG [In log]: vanbot Hello
[Sat Jan 07 2017 16:24:39 GMT+0000 (UTC)] DEBUG Started global js socketIO client for SLACK at 6466
[Sat Jan 07 2017 16:24:39 GMT+0000 (UTC)] DEBUG Added a callback to hasher for global-client
[Sat Jan 07 2017 16:24:39 GMT+0000 (UTC)] DEBUG Added a callback to hasher for global-client
[Sat Jan 07 2017 16:24:39 GMT+0000 (UTC)] DEBUG IO on pass, msg: {
"hash": "global-client-js_2324eb73fbc0094b55432d9359a4ab3b",
"from": "global-client-js",
"input": "Hello",
"to": "nlp.cgkb-py",
"intent": "parse"
} fn: undefined
[Sat Jan 07 2017 16:24:39 GMT+0000 (UTC)] DEBUG IO on pass, msg: {
"hash": "global-client-js_ff6ce27311a4ae863af18b6a29d2d3c8",
"from": "global-client-js",
"input": "Hello",
"to": "convo_classifier.py",
"intent": "classify"
} fn: undefined
[Sat Jan 07 2017 16:24:39 GMT+0000 (UTC)] INFO global-client-js VYpSvkXutD82Y6j0AAAC joined, -2 remains
[Sat Jan 07 2017 16:24:39 GMT+0000 (UTC)] INFO All 5 IO clients have joined
[Sat Jan 07 2017 16:24:59 GMT+0000 (UTC)] ERROR
global-client-js promise exception with input: undefined, to: {"input":"Hello","to":"nlp.cgkb-py","intent":"parse"}
global-client-js promise exception with input: undefined, to: {"input":"Hello","to":"convo_classifier.py","intent":"classify"}
This is the thread for discussing the proper dockerization of AIVA. The current master is stable and can begin to be dockerized.
However, when the CGKB branch is merged we'd need to add new dependencies and process control, as it interacts at core with python (spaCy NLP), uses the neo4j graph database for the brain, and socket IO server for node-python communication.
I've installed the hubot socket.io adapter as I would like to implement a chatbot which talks to a socket.io server.
How do I get AIVA to use this adapter?
Many thanks!
Hello, I'm trying to make it work but I have this error that I couldn't find out where comes from:
[Wed Oct 19 2016 13:44:58 GMT+0200 (CEST)] ERROR Unable to load /home/user/GitHub/aiva/scripts/_init: TypeError: polyIO.Client is not a function
I think that configuration is working well, debug before that line is:
[Wed Oct 19 2016 13:44:53 GMT+0200 (CEST)] INFO Starting poly-socketio server on port: 6466, expecting 3 IO clients
[Wed Oct 19 2016 13:44:53 GMT+0200 (CEST)] DEBUG adapterConfig {
"ACTIVATE": true,
"HUBOT_SLACK_TOKEN": "-mytoken-"
}
[Wed Oct 19 2016 13:44:53 GMT+0200 (CEST)] DEBUG import js lib from client.js
[Wed Oct 19 2016 13:44:53 GMT+0200 (CEST)] INFO Starting socketIO client for js at 6466
[Wed Oct 19 2016 13:44:53 GMT+0200 (CEST)] INFO Starting socketIO client for python3 at 6466
[Wed Oct 19 2016 13:44:53 GMT+0200 (CEST)] DEBUG Set SLACK PORT: 8345
[Wed Oct 19 2016 13:44:53 GMT+0200 (CEST)] DEBUG No WEBHOOK set for adapter SLACK
[Wed Oct 19 2016 13:44:53 GMT+0200 (CEST)] INFO Deploying bot aivadev with adapter SLACK
[Wed Oct 19 2016 13:44:53 GMT+0200 (CEST)] DEBUG js YjBROj4Z-tFL-zDOAAAA joined, 2 remains
[Wed Oct 19 2016 13:44:54 GMT+0200 (CEST)] DEBUG py 2q3FQ61SQCHDERP8AAAB joined, 1 remains
[Wed Oct 19 2016 13:44:56 GMT+0200 (CEST)] INFO Logged in as bot1_test_cs of Geo-C
[Wed Oct 19 2016 13:44:57 GMT+0200 (CEST)] INFO Slack client now connected
I hope you can help me. thanks
Alright, ubuntu install got me maybe 90% of the way but as noted in previous issue: no joy (yet).
So, a-docker-ing we go.
Got it online. Easy peasy.
But I end up in the /opt/aiva directory but nothing is there. Is the :latest version not ready any longer? How do I use this once it is running?
Thanks!
Hi All,
I know this is an old project and many of the components have changed since it was written i.e. Slack doesn't use tokens anymore.
Has anyone managed to get this Aiva platform running lately? I'm working on a similar project and this would be incredibly useful to have a working version.
Hey there,
I've used dockerized version and aivadev is up and running. It replies to hello-io py etc. But when I ask nlp demo 1 or nlp demo 2 nothing happens.
What am I missing here? Do I need to manually install or run something?
thanks in advance,
Tamir.
Hi,
How do we return a default reply for all inputs that does not have a handling intent?
E.g. I pass "blah" as input. Their is no intent to handle this, hence I want to return a default reply to the user.
Thanks & Regards
Hi, I am trying to install the cgkb demo. I got the following:
npm modules already installed
[Fri Mar 16 2018 16:52:55 GMT-0700 (PDT)] ERROR {
"0": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MySQL client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MySQL client",
"sqlState": "08004",
"fatal": true
}
},
"1": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MySQL client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MySQL client",
"sqlState": "08004",
"fatal": true
}
},
"2": {
"name": "SequelizeConnectionError",
"message": "ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client",
"parent": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MySQL client",
"sqlState": "08004",
"fatal": true
},
"original": {
"code": "ER_NOT_SUPPORTED_AUTH_MODE",
"errno": 1251,
"sqlMessage": "Client does not support authentication protocol requested by server; consider upgrading MySQL client",
"sqlState": "08004",
"fatal": true
}
},
"length": 3
}
Sequelize [Node: 6.7.0, CLI: 2.8.0, ORM: 3.32.1]
Loaded configuration file "config/db.json".
Using environment "development".
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client
Sequelize [Node: 6.7.0, CLI: 2.8.0, ORM: 3.32.1]
Loaded configuration file "config/db.json".
Using environment "test".
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client
Sequelize [Node: 6.7.0, CLI: 2.8.0, ORM: 3.32.1]
Loaded configuration file "config/db.json".
Using environment "production".
Unable to connect to database: SequelizeConnectionError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client
npm ERR! Linux 4.4.0-116-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "setup"
npm ERR! node v6.7.0
npm ERR! npm v3.10.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] setup: bin/setup
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] setup script 'bin/setup'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the aiva package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! bin/setup
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs aiva
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls aiva
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/amir/repos/aiva/npm-debug.log
here is from log file:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'setup' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'presetup', 'setup', 'postsetup' ]
5 info lifecycle [email protected]presetup: [email protected]presetup: no script for presetup, continuing
6 silly lifecycle [email protected]
7 info lifecycle [email protected]setup: [email protected]setup: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]setup: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/amir/repos/aiva/node_modules/.bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/binsetup: CWD: /home/amir/repos/aiva
10 verbose lifecycle [email protected]
11 silly lifecycle [email protected]setup: Args: [ '-c', 'bin/setup' ]setup: Returned: code: 1 signal: null
12 silly lifecycle [email protected]
13 info lifecycle [email protected]~setup: Failed to exec setup script
14 verbose stack Error: [email protected] setup: bin/setup
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:242:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:877:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/amir/repos/aiva
17 error Linux 4.4.0-116-generic
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "setup"
19 error node v6.7.0
20 error npm v3.10.3
21 error code ELIFECYCLE
22 error [email protected] setup: bin/setup
22 error Exit status 1
23 error Failed at the [email protected] setup script 'bin/setup'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the aiva package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error bin/setup
23 error You can get information on how to open an issue for this project with:
23 error npm bugs aiva
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls aiva
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
There's an error about socketIO client when I start the aiva. The following is the log:
[Mon Jun 11 2018 13:53:34 GMT+0000 (UTC)] INFO Authenticated database successfully
[Mon Jun 11 2018 13:53:36 GMT+0000 (UTC)] INFO Starting aiva process
[Mon Jun 11 2018 13:53:36 GMT+0000 (UTC)] INFO Starting poly-socketio server on port: 6466, expecting 4 IO clients
[Mon Jun 11 2018 13:53:36 GMT+0000 (UTC)] INFO Starting socketIO client for js at 6466
[Mon Jun 11 2018 13:53:36 GMT+0000 (UTC)] INFO Starting socketIO client for python at 6466
[Mon Jun 11 2018 13:53:36 GMT+0000 (UTC)] INFO Deploying bot aivadev with adapter SLACK
[Mon Jun 11 2018 13:53:36 GMT+0000 (UTC)] INFO Starting socketIO client for python at 6466
./bin/hubot: line 8: /Users/Shawn/SourceCode/github/aiva/node_modules/.bin/hubot: No such file or directory
[Mon Jun 11 2018 13:53:36 GMT+0000 (UTC)] INFO js pfMFAodYAxkGm0VwAAAA joined, 3 remains
[Mon Jun 11 2018 13:53:43 GMT+0000 (UTC)] ERROR Traceback (most recent call last):
File "/Users/Shawn/SourceCode/github/aiva/lib/client.py", line 89, in
[Mon Jun 11 2018 13:53:43 GMT+0000 (UTC)] ERROR client = SocketIO('localhost', int(IOPORT))
File "/usr/local/lib/python2.7/site-packages/socketIO_client/init.py", line 353, in init
resource, hurry_interval_in_seconds, **kw)
File "/usr/local/lib/python2.7/site-packages/socketIO_client/init.py", line 54, in init
self._transport
File "/usr/local/lib/python2.7/site-packages/socketIO_client/init.py", line 62, in _transport
self._engineIO_session = self._get_engineIO_session()
File "/usr/local/lib/python2.7/site-packages/socketIO_client/init.py", line 76, in _get_engineIO_session
transport.recv_packet())
StopIteration
So how can I fix it? Any ideas? Thanks.
I'm trying to get AIVA running on a Docker instance on my Windows machine (I know, I know). npm start is giving me a SequelizeConnection error. It looks like the Dockerfile is setup with postgres in mind, but the AIVA config has been updated to use mysql.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.