System.UriFormatException: Invalid URI: The hostname could not be parsed.

[tarzzzan]

Hello Archi! Big THX for you work!!!
But I need you help.

I run ASF on small VPS, all works fine on V2.2.1.6, but start from V2.2.1.7 (and all next version) get same error:

[ERROR] FATAL UNHANDLED EXCEPTION: System.AggregateException: One or more errors occurred. ---> System.UriFormatException: Invalid URI: The hostname could not be parsed.
at System.Uri.CreateThis (System.String uri, System.Boolean dontEscape, System.UriKind uriKind) [0x00090] in <5071a6e4a4564e19a2eda0f53e42f9bd>:0
at System.Uri..ctor (System.String uriString) [0x00017] in <5071a6e4a4564e19a2eda0f53e42f9bd>:0
at NLog.Config.ConfigurationItemFactory.BuildDefaultFactory () [0x00033] in <294b42a9e7eb4ed898baa93ed17d3c81>:0
at NLog.Config.ConfigurationItemFactory.get_Default () [0x00007] in <294b42a9e7eb4ed898baa93ed17d3c81>:0
at NLog.Targets.Target.Register (System.String name, System.Type targetType) [0x00000] in <294b42a9e7eb4ed898baa93ed17d3c81>:0
at NLog.Targets.Target.Register[T] (System.String name) [0x0000b] in <294b42a9e7eb4ed898baa93ed17d3c81>:0
at ArchiSteamFarm.Program+<Init>d__29.MoveNext () [0x00031] in <8e2c5bf04c21476991605cd1e2f2f8aa>:0
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00014] in <8f2c484307284b51944a1a13a14c0266>:0
at System.Threading.Tasks.Task.Wait (System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00052] in <8f2c484307284b51944a1a13a14c0266>:0
at System.Threading.Tasks.Task.Wait () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0
at ArchiSteamFarm.Program.Main (System.String[] args) [0x0000d] in <8e2c5bf04c21476991605cd1e2f2f8aa>:0
---> (Inner Exception #0) System.UriFormatException: Invalid URI: The hostname could not be parsed.
at System.Uri.CreateThis (System.String uri, System.Boolean dontEscape, System.UriKind uriKind) [0x00090] in <5071a6e4a4564e19a2eda0f53e42f9bd>:0
at System.Uri..ctor (System.String uriString) [0x00017] in <5071a6e4a4564e19a2eda0f53e42f9bd>:0
at NLog.Config.ConfigurationItemFactory.BuildDefaultFactory () [0x00033] in <294b42a9e7eb4ed898baa93ed17d3c81>:0
at NLog.Config.ConfigurationItemFactory.get_Default () [0x00007] in <294b42a9e7eb4ed898baa93ed17d3c81>:0
at NLog.Targets.Target.Register (System.String name, System.Type targetType) [0x00000] in <294b42a9e7eb4ed898baa93ed17d3c81>:0
at NLog.Targets.Target.Register[T] (System.String name) [0x0000b] in <294b42a9e7eb4ed898baa93ed17d3c81>:0
at ArchiSteamFarm.Program+<Init>d__29.MoveNext () [0x00031] in <8e2c5bf04c21476991605cd1e2f2f8aa>:0 <---

+info:
latest version of mono (4.6.2)
Ubuntu 14.04.5 LTS main, just make fresh install on 16.04.2 LTS = all same errors "Invalid URI"

[Archi]

It works for me:

archi@archi:~/ArchiSteamFarm/ArchiSteamFarm/bin/Release$ mono ArchiSteamFarm.exe --server
2017-02-14 04:28:07|INFO|ASF|InitASF() ASF V2.2.2.7
2017-02-14 04:28:08|INFO|ASF|IsRuntimeSupported() Your Mono runtime version is OK.
2017-02-14 04:28:08|INFO|ASF|IsRuntimeSupported() Required version: 4.6 | Found version: 4.6.2
2017-02-14 04:28:08|INFO|ASF|StartServer() Starting WCF server on net.tcp://127.0.0.1:1242/ASF...
2017-02-14 04:28:09|INFO|ASF|StartServer() WCF server ready!

What is your WCFHost, WCFPort and WCFBinding?

Full log would answer that btw.

[Archi]

Also I can't see any changes between 2.2.1.6 and 2.2.1.7 that could affect invalid URLs being generated. If you can reproduce it with latest stable or pre-release, then please post full log, so I can see all the info I need. Using anything else is out of support anyway, even if it makes sense to spot first ASF version that is broken (but very often it's just a coincidence, otherwise I can read from the code what changed, and I can't in this case).

[tarzzzan]

in asf folder - log.txt empty... asf crash on start

NLog.config default:

 
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <targets>
    <target xsi:type="ColoredConsole" name="ColoredConsole" detectConsoleAvailable="false" layout="${date:format=yyyy-MM-dd HH\:mm\:ss}|${processname}-${processid}|${level:uppercase=true}|${logger}|${message}${onexception:inner= ${exception:format=toString,Data}}" />
    <target xsi:type="EventLog" name="EventLog" layout="${logger}|${message}${onexception:inner= ${exception:format=toString,Data}}" log="ArchiSteamFarm" source="Logger" />
    <target xsi:type="File" name="File" deleteOldFileOnStartup="true" fileName="log.txt" layout="${date:format=yyyy-MM-dd HH\:mm\:ss}|${processname}-${processid}|${level:uppercase=true}|${logger}|${message}${onexception:inner= ${exception:format=toString,Data}}" />
  </targets>

  <rules>
    <logger name="*" minlevel="Debug" writeTo="ColoredConsole" />
    <logger name="*" minlevel="Debug" writeTo="EventLog" />
    <logger name="*" minlevel="Debug" writeTo="File" />
  </rules>
</nlog>

deleteOldFileOnStartup - change to "false" for test = same emrty


All WCF settings - default, and i don't use it:

 "WCFBinding": 0,
 "WCFHost": "127.0.0.1",
 "WCFPort": 1242

Archi の投稿を引用：

Also I can't see any changes between 2.2.1.6 and 2.2.1.7 that could affect invalid URLs being generated.

Invalid URI in my case, not URL

[Archi]

Why are you logging to event log and using default NLog config? I stated quite clearly on ASF wiki to not use it if you don't wish to make any changes in it. Delete it so ASF uses default logging and then include full log.txt.

[tarzzzan]

Found this:

02/14/2017 08:15:49ASF V2.2.2.6 has run into fatal exception before core logging module was even able to initialize!
Exception: UnhandledExceptionHandler() One or more errors occurred.
StackTrace:
  at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00014] in <8f2c484307284b51944a1a13a14c0266>:0 
  at System.Threading.Tasks.Task.Wait (System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00052] in <8f2c484307284b51944a1a13a14c0266>:0 
  at System.Threading.Tasks.Task.Wait () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0 
  at ArchiSteamFarm.Program.Main (System.String[] args) [0x0000d] in <8e2c5bf04c21476991605cd1e2f2f8aa>:0 Exception: UnhandledExceptionHandler() Invalid URI: The hostname could not be parsed.
StackTrace:
  at System.Uri.CreateThis (System.String uri, System.Boolean dontEscape, System.UriKind uriKind) [0x00090] in <5071a6e4a4564e19a2eda0f53e42f9bd>:0 
  at System.Uri..ctor (System.String uriString) [0x00017] in <5071a6e4a4564e19a2eda0f53e42f9bd>:0 
  at NLog.Config.ConfigurationItemFactory.BuildDefaultFactory () [0x00033] in <294b42a9e7eb4ed898baa93ed17d3c81>:0 
  at NLog.Config.ConfigurationItemFactory.get_Default () [0x00007] in <294b42a9e7eb4ed898baa93ed17d3c81>:0 
  at NLog.Targets.Target.Register (System.String name, System.Type targetType) [0x00000] in <294b42a9e7eb4ed898baa93ed17d3c81>:0 
  at NLog.Targets.Target.Register[T] (System.String name) [0x0000b] in <294b42a9e7eb4ed898baa93ed17d3c81>:0 
  at ArchiSteamFarm.Program+<Init>d__29.MoveNext () [0x00031] in <8e2c5bf04c21476991605cd1e2f2f8aa>:0 

[Archi]

https://github.com/JustArchi/ArchiSteamFarm/issues/292

This has nothing to do with WCF, this is NLog issue.

[Archi]

I'll give you custom NLog.config which would tell me what is the problem of this issue, sec.

[tarzzzan]

Ok, full read and see exactly my problem
Now i remember - why i use NLog.config
Sadly what can't use newest version with OptimizationMode ^^

so... sit back and wait NLog fix it
Thx for you time!!! Its really good to see whats problem not in my hands =)

[Archi]

This is NLog issue that should be fixed, I reported it already - https://github.com/NLog/NLog/issues/1965

Due to the fact that I can't reproduce it, you must help me in generating internal log for this problem, so we can see where the issue is. Do it like this:

archi@archi:~/ASF/test$ export NLOG_INTERNAL_LOG_LEVEL=Trace
archi@archi:~/ASF/test$ export NLOG_INTERNAL_LOG_FILE=nlog.txt
archi@archi:~/ASF/test$ mono ASF.exe

After ASF crash, upload entire content of nlog.txt (and I hope it'll be created, the crash is so early that internal module might not even be able to initialize).

[tarzzzan]

Archi の投稿を引用：

I'll give you custom NLog.config which would tell me what is the problem of this issue, sec.

Ok, lets try some magic =)

[Archi]

Instructions above ^

[tarzzzan]

NLog.config from post #3
nlog.txt - http://pastebin.com/Q5sDrkcm

[Archi]

I can't see any ASF/NLog crash here, did you reproduce the problem? Also you shouldn't use any custom NLog.config when creating internal log for debugging, it complicates everything.

[tarzzzan]

if i remove NLog.config... no nlog.txt

issues 292

 GUiHKX commented on 4 Aug 2016 • edited

Just want to give an update on this:

If you do not have a NLog.config file and you try run ASF as a systemd service, it won't work	

[Archi]

Okay, but that is a workaround and not a fix, thanks for info about lack of nlog.txt, it helps a lot. Hopefully I'll solve it with NLog devs, while in the meantime you can use mentioned workaround to make ASF work.