Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 14 02:53
    wmowm commented #459
  • Oct 12 15:59
    niemyjski commented #459
  • Oct 12 15:57
    niemyjski edited #459
  • Oct 12 12:54
    niemyjski synchronize #452
  • Oct 12 12:54

    niemyjski on elastic7

    Fixed serializer null reference… Fixed all Swagger issues. (compare)

  • Oct 12 12:26
    niemyjski synchronize #452
  • Oct 12 12:26

    niemyjski on elastic7

    Updated to latest foundatio rep… (compare)

  • Oct 12 12:24
    niemyjski synchronize #452
  • Oct 12 12:24

    niemyjski on elastic7

    Fixed elasticsearch serializer … (compare)

  • Oct 12 11:01
    wmowm opened #459
  • Oct 11 11:21
    niemyjski commented #458
  • Oct 10 21:18
    kiquenet opened #458
  • Oct 10 13:30
    niemyjski updated the wiki
  • Oct 10 09:20
  • Oct 10 03:36
  • Oct 09 15:54
    john-roland closed #456
  • Oct 09 15:54
    john-roland commented #456
  • Oct 09 14:12
    niemyjski labeled #457
  • Oct 09 14:12
    niemyjski labeled #457
  • Oct 09 14:12
    niemyjski commented #457
Blake Niemyjski
@niemyjski
we are trying to make it a painless process in the future
Lukas Wöhrl
@woehrl01
C:\exceptionless.api\App_Data\JobRunner>Job.bat -t "Exceptionless.Core.Jobs.StackMigrationJob, Exceptionless.EventMigration" -s "Exceptionless.Core.Jobs.JobBootstrapper, Exceptionless.Core"
this doesn't work
could you please tell me, whats possible wrong :)
Blake Niemyjski
@niemyjski
Do Job.exe instead of bat
Lukas Wöhrl
@woehrl01
2015-06-11 16:25:15.6358|ERROR|TypeHelper|Unable to resolve type:
is the error
Blake Niemyjski
@niemyjski
Exceptionless.EventMigration.StackMigrationJob
your type is wrong
any chance you could paste all the commands you used when you are done and I'll put it in a gist
Job.exe -t "Exceptionless.EventMigration.StackMigrationJob, Exceptionless.EventMigration" -s "Exceptionless.Core.Jobs.JobBootstrapper, Exceptionless.Core"
Job.exe -t "Exceptionless.EventMigration.QueueEventMigrationsJob, Exceptionless.EventMigration" -s "Exceptionless.Core.Jobs.JobBootstrapper, Exceptionless.Core"
Job.exe -t "Exceptionless.EventMigration.EventMigrationJob, Exceptionless.EventMigration" -s "Exceptionless.Core.Jobs.JobBootstrapper, Exceptionless.Core"
Lukas Wöhrl
@woehrl01

System.AggregateException: Mindestens ein Fehler ist aufgetreten. ---> System.Nu
llReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festg
elegt.
bei Foundatio.Jobs.JobRunner.<RunAsync>d5.MoveNext()
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCancele
dExceptions)
bei System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotific ation) bei System.Threading.Tasks.Task1.get_Result()
bei Foundatio.JobRunner.Program.Main(String[] args) in c:\projects\foundatio\
src\JobRunner\Program.cs:Zeile 31.
---> (Interne Ausnahme #0) System.NullReferenceException: Der Objektverweis wurd
e nicht auf eine Objektinstanz festgelegt.
bei Foundatio.Jobs.JobRunner.<RunAsync>d
5.MoveNext()<---

2015-06-11 16:29:51.2693|ERROR|JobRunner|Unable to create job instance.
2015-06-11 16:29:51.3270|ERROR|Program|Job "EventMigrationJob" error: Der Objekt
verweis wurde nicht auf eine Objektinstanz festgelegt.

this happens on QueueEventMigrationsJob and EventMigrationJob, the first one is working fine
Blake Niemyjski
@niemyjski
ah
not 100% sure
let me look
Lukas Wöhrl
@woehrl01
ok
Blake Niemyjski
@niemyjski
ah
you don't need the -s on the end
did that help?
blob
I just ran them and they worked
The thing is open the job.exe.config and set the redis connection string
Lukas Wöhrl
@woehrl01
yep, seems without -s its working, I'l report when they are finished
Blake Niemyjski
@niemyjski
I just thought about that
because you need to queue the migrations to someplace (default is in memory)
and that doesn't really work when you have multiple processes
@woehrl01 we just added the -s flag in the latest nightly hehe
Lukas Wöhrl
@woehrl01
I just executed those, but still no additional exceptions :-/
Blake Niemyjski
@niemyjski
you'll need to configure redis
otherwise the queue event migrations job is just going to queue things to nothing
(in memory queue)
Did the stacks show up in your elastic search instance
Lukas Wöhrl
@woehrl01
no, the stacks are not showing up
I just renabled redis but still no exceptionions
so. I changed job.exe.config to the same values aus web.config (mongodb/redis/elastic) and I reexecuted the statements above for StackMigrationJob, QueueEventMigrationsJob and EventMigrationJob
but, the old exceptions are still not showing up
any further suggestions?
Lukas Wöhrl
@woehrl01
I just enabled, the INFO logging level. and it prints the following: The daterange looks a little bit off?
2015-06-11 17:14:30.9660|INFO|JobRunner|Starting job type "EventMigrationJob" on machine "VM9-DEV"...
2015-06-11 17:14:31.1126|WARN|Bootstrapper|StatsD Metrics is NOT enabled.
2015-06-11 17:14:31.2572|WARN|Bootstrapper|Azure Storage is NOT enabled.
2015-06-11 17:14:32.8286|INFO|MigrationJobBase|Public IP: 79.255.159.7
2015-06-11 17:14:32.8579|INFO|EventMigrationJob|Processing event migration jobs
for date range: 2014-07-31T00:00:00.0000000+00:00-2014-07-31T12:00:00.0000000+00:00
2015-06-11 17:14:33.4149|INFO|EventMigrationJob|Finished processing event migration jobs for date range: 2014-07-31T00:00:00.0000000+00:00-2014-07-31T12:00:00.0000000+00:00
Blake Niemyjski
@niemyjski
Yeah that is good it's doing 12 hour day increments
that looks good
anything in the log for migrating stacks
If you want I could jump on a remote meeting for a few minutes and help take a look
Lukas Wöhrl
@woehrl01
yeah, I cleared redis and did all of this again, and with info enabled I get:
2015-06-11 17:21:57.3987|INFO|StackMigrationJob|Migrating stacks 8.000 total 2.711/s...
2015-06-11 17:21:57.4192|INFO|StackMigrationJob|Migrating stacks 8.050 total 2.711/s... etc
looks good so far, except that it's not showing :D
Blake Niemyjski
@niemyjski
we'll what are you using to look at your elastic search content