Hi, thanks for your response. I've looked through the doc and made all the changes I could see. I rechecked the line endings of all the files in the config and scripts directory, all are unix LF.
Actually, I had waited for a few minutes before concluding that there was "no response" to +help and "stuck at logging in after sending password", but after a while I decided to wait a while longer. I noticed that the response would come almost exactly 15 minutes after the input, not that it never comes. To clarify, --> login with a unregistered nick -> immediate connection -> type +regme test or +help or anything -> about 15 minutes and a few seconds later -> expected response. --> login with a registered nick -> waits at "stored password sent" for 15 minutes + a second or two, then proceeds as expected. type anything after that, it takes either a few seconds, or exactly 15 minutes, for a response. For example, when I connected with an registered nick (and tried another nick with the same client): [05-22-17 13:13:08] *** Connecting to adc://10.3.11.111:2781 ... [05-22-17 13:13:08] *** Connected [05-22-17 13:28:09] <TITAN> This hub is running ADCH++ 2.12.1 (r"[unknown]") Debug [05-22-17 13:28:09] <TITAN> Registration data updated (new nick) [05-22-17 13:28:09] <TITAN> Welcome back [05-22-17 13:28:09] <TITAN> Displaying the last 0 messages [05-22-17 13:28:09] <TITAN> Hub description content goes here [05-22-17 13:28:09] <TITAN> MOTD content goes here [05-22-17 13:28:09] <TITAN> Rules content goes here [05-22-17 13:48:33] <dwqsada> . [05-22-17 13:48:33] <dwqsada> . There is a 15 minute delay after entering the password and the hub connecting. The network between them is fine throughout however. The dc client is airdc++ 3.40 on windows 10, the host is a raspberry pi 2b, both are on the same lan (connected to the same router by lan cable), have tested about 40-60mbits of network throughput between them, ping <2ms as expected, no load on the rpi and nothing else past a few percent of cpu load running on it. >From what I've read in the doc I've made the needed linux changes, and the hub does work apart from the 15minute lag. I can regnick and +test and so forth with a 15 minute delay, and I also get the history of mainchat from the history.lua script (immediately when logging in with an unregistered user) For reference, debug log: pi@artypi:~/titanadc/bin $ ./adchppd -c /home/pi/titanadc/bin/config Starting. Core initialized .Processing HubName Processing Description Processing Log Processing LogFile Processing MaxCommandSize Processing BufferSize Processing MaxBufferSize Processing OverflowTimeout Processing DisconnectTimeout Processing LogTimeout . 2.12.1 (r"[unknown]") Debug running, press ctrl-c to exit... Logging: 2017-05-22 15:07:44: ScriptManager: Starting Logging: 2017-05-22 15:07:44: PluginManager: Script.so loaded Logging: 2017-05-22 15:07:44: BloomManager: Starting Logging: 2017-05-22 15:07:44: PluginManager: Bloom.so loaded Logging: 2017-05-22 15:07:44: SocketManager: Starting Logging: 2017-05-22 15:07:44: SocketManager: Listening on 0.0.0.0:2780 (Encrypted: Yes) Logging: 2017-05-22 15:07:44: SocketManager: Listening on [::]:2780 (Encrypted: Yes) Logging: 2017-05-22 15:07:44: SocketManager: Listening on 0.0.0.0:2781 (Encrypted: No) Logging: 2017-05-22 15:07:44: SocketManager: Listening on [::]:2781 (Encrypted: No) EMMD entering IDENTIFY EMMD entering NORMAL FPPI entering IDENTIFY FPPI entering NORMAL 2QY2 connected 2QY2 ready 2QY2 entering IDENTIFY 2QY2 verifying IP 0.0.0.0 2QY2 verifying CID R3ZRC4U7H2LU3WASRXRJYY2PRHB7XDV6V3YFWQY 2QY2 verifying nick TheLastGuardian 2QY2 entering NORMAL I'm not sure what is the cause of the exact 15 minute delay between input/connection and response. I'll try hosting the hub on a normal x64 linux laptop to see if the issue persists there as well. Any ideas? Thanks. -- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to ADCH++. https://bugs.launchpad.net/bugs/1692364 Title: unable to compile recent adchpp builds on linux Status in ADCH++: Invalid Bug description: Hi. I've been trying to run a adchpp hub (migrating from ptokax). The provided Windows binaries for the latest version 2.12.1 works fine, but compiling the source for this newest version on linux fails. I've tried compiling on Ubuntu 14.04/16.04 x64 (inbuilt in windows 10 bash-on-windows), on Debian Jessie x64, and Raspbian Jessie on my raspberry pi 2B (arm). I referred to this question posted 3-4 years ago https://answers.launchpad.net/adchpp/+question/236015 which provided the info to remove the two lines in SConstruct to get the build compiling. However the binary generated does not run correctly: adchpp_2.12.1_source/build/debug-default-x64/bin] ./adchppd Starting. Core initialized .Thrown: FileException: Could not open file Unable to load adchpp.xml, using defaults: FileException: Could not open file . 2.12.1 (r"[unknown]") Debug running, press ctrl-c to exit... Logging: 2017-05-21 21:16:16: SocketManager: Starting Thrown: FileException: Could not open file LogManager::log: FileException: Could not open file Thrown: FileException: Could not open file LogManager::log2: FileException: Could not open file ^CLogging: 2017-05-21 21:16:20: core: Shutting down... Thrown: FileException: Could not open file LogManager::log: FileException: Could not open file Thrown: FileException: Could not open file LogManager::log2: FileException: Could not open file Shut downBusy pool objects: 0 I've pasted the scripts files and config files as required (in the same way as in the windows build of adchpp, where it works fine) I can paste the entire compile log if needed (it seems to compile fine, with # collect2 0.68 0.06 Move("build/debug-default/bin/socket/core.so", "build/debug-default/lua/LuaSocket/socket/core.so") scons: done building targets. at the end) ^This is from my rpi arm build, I've also tried x64 debug build and x64 release build options with the same apparent success in compilation. I also tried manually doing chmod 777 to all files in the build folder and running as sudo, still the same issues, seems to not be compiling properly. To manage notifications about this bug go to: https://bugs.launchpad.net/adchpp/+bug/1692364/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
