iamthesq Posted December 11, 2018 Posted December 11, 2018 After running the Pi install script, NodeLink doesn't want to start up. It shows a password error and that the hostname (polyglot) can't be parsed. Any ideas? Here's the output. pi@polyglot:~ $ sudo curl -sSL http://automationshack.com/Files/install.sh | bash ### Installing dirmngr and updating to offical mono repo dirmngr is already the newest version (2.1.18-8~deb9u3). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Executing: /tmp/apt-key-gpghome.939uxBNG9U/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF key A6A19B38D3D831EF: 2 signatures not checked due to missing keys gpg: key A6A19B38D3D831EF: "Xamarin Public Jenkins (auto-signing) <releng@xamarin.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 deb http://download.mono-project.com/repo/debian raspbianstretch main ### Updating System - this may take several minutes All packages are up to date. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Installing mono and relevant dependencies - this may take several minutes libmono-system-net-http-formatting4.0-cil is already the newest version (5.16.0.220-0xamarin4+raspbian9b1). libmono-system-net-http-webrequest4.0-cil is already the newest version (5.16.0.220-0xamarin4+raspbian9b1). libmono-system-net-http4.0-cil is already the newest version (5.16.0.220-0xamarin4+raspbian9b1). mono-vbnc is already the newest version (4.7-0xamarin1+raspbian9b1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Creating directory ### Downloading NodeLink ### Modifying startup script ### Starting NodeLink ### Install complete. Login to NodeLink at http://10.0.1.42:8090 pi@polyglot:~ $ 2018-12-11 00:07:12 - ISY NodeLink Server v0.9.24 started 2018-12-11 00:07:12 - OS: Linux polyglot 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux 2018-12-11 00:07:12 - Mono version: 5.16.0.220 (tarball Mon Nov 26 17:53:18 UTC 2018) 2018-12-11 00:07:13 - Web config server started (http://10.0.1.42:8090) 2018-12-11 00:07:13 - No password specified for the ISY Unhandled Exception: System.UriFormatException: Invalid URI: The hostname could not be parsed. at System.Uri.CreateThis (System.String uri, System.Boolean dontEscape, System.UriKind uriKind) [0x0007b] in <c0e40d34c25e4827874530676d4126b9>:0 at System.Uri..ctor (System.String uriString) [0x00014] in <c0e40d34c25e4827874530676d4126b9>:0 at NodeLink.RestISY.a (System.String A_0, System.Boolean A_1) [0x0009a] in <3cfda86346df48819a7b88da9fabba44>:0 at NodeLink.RestISY.b (System.String A_0, System.Boolean A_1) [0x0000e] in <3cfda86346df48819a7b88da9fabba44>:0 at NodeLink.RestISY.GetDescription () [0x00000] in <3cfda86346df48819a7b88da9fabba44>:0 at NodeLink.RestISY..ctor (System.String user, System.String password, System.String address, System.Boolean SSL) [0x00687] in <3cfda86346df48819a7b88da9fabba44>:0 at i.m () [0x00855] in <3cfda86346df48819a7b88da9fabba44>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.UriFormatException: Invalid URI: The hostname could not be parsed. at System.Uri.CreateThis (System.String uri, System.Boolean dontEscape, System.UriKind uriKind) [0x0007b] in <c0e40d34c25e4827874530676d4126b9>:0 at System.Uri..ctor (System.String uriString) [0x00014] in <c0e40d34c25e4827874530676d4126b9>:0 at NodeLink.RestISY.a (System.String A_0, System.Boolean A_1) [0x0009a] in <3cfda86346df48819a7b88da9fabba44>:0 at NodeLink.RestISY.b (System.String A_0, System.Boolean A_1) [0x0000e] in <3cfda86346df48819a7b88da9fabba44>:0 at NodeLink.RestISY.GetDescription () [0x00000] in <3cfda86346df48819a7b88da9fabba44>:0 at NodeLink.RestISY..ctor (System.String user, System.String password, System.String address, System.Boolean SSL) [0x00687] in <3cfda86346df48819a7b88da9fabba44>:0 at i.m () [0x00855] in <3cfda86346df48819a7b88da9fabba44>:0
UrcH Posted December 13, 2018 Posted December 13, 2018 I have the same problem with System.UriFormatException: Invalid URI: The hostname could not be parsed.
io_guy Posted December 13, 2018 Posted December 13, 2018 Odd, I'll have to wrap some error handling around that in the next version. Never seen it before. You could try adding ISY and its IP to /etc/hosts.
UrcH Posted December 13, 2018 Posted December 13, 2018 That worked! Thanks! First time trying this. Thanks for the quick response. I am so excited!
io_guy Posted December 13, 2018 Posted December 13, 2018 Glad to hear it. To help my debugging, what was your hostnane that didn't work?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.