Mark Henderson

Jun 11, 2019 23:55
@DavidRicherby I've had multiple US Visas and apart from when CBP messed up my i94 exit date has always coincided with my visa expiry. It still seems foolish to book a ticket for after a visa has expired.
Jun 11, 2019 23:55
@abagail unfortunately they do this with scary regularity. I once found I was overstaying my i94 by months becusse the agent made a mistake when typing it in. Took weeks to fix. However in this case the op says the visa expires on the 25th so they never should have booked a ticket for the 28th.
 
May 30, 2018 04:13
For those of us who don't speak science, is the OPs partner right?
 
Sep 24, 2017 21:30
FWIW when I take my kids into Times Square I look and sound like a tourist, even though I’m not, and that hip hop CD scam is the only one I paid money to escape from. It’s very intimidating. Don’t beat yourself up - there’s a reason it’s so successful.
 
Mar 18, 2017 03:31
Haha. As an Australian living in the US almost everyone I meet assumes I'm British. It happens so often I just go along with it, takes too much effort to keep correcting people.
 
Nov 25, 2016 21:57
@teego1967 rubbish. It entirely depends on your company and its culture. Where I work, it's not uncommon to see staff in their 30s playing video games before or after work, sometimes on their lunch breaks. Sweeping statements like yours are outdated, especially depending on where you work.
 
Oct 25, 2016 15:44
Good luck
Oct 25, 2016 15:43
Hopefully you can find it by exploring the docs themselves
Oct 25, 2016 15:43
That's all I can do I'm afraid. I'm 99% sure there's just something simple wrong in the documents, because I haven't seen kibana "miss" documents before
Oct 25, 2016 15:42
It's more forgiving than Kibana, but doesn't do visualisations or that sort of stuff
Oct 25, 2016 15:42
I'd try and get that plugin installed and see if you can query your data through that UI instead.
Oct 25, 2016 15:40
Just trying to find it
Oct 25, 2016 15:40
There is an Elastic plugin that allows you to actually browse the data differently
Oct 25, 2016 15:39
Still got "last 5 years" selected?
Oct 25, 2016 15:38
That's not very many
Oct 25, 2016 15:37
ok
Oct 25, 2016 15:37
It might be useful to just see whats actually inside the index
Oct 25, 2016 15:37
Otherwise, the browser plugin sense will allow you to query your data with more power (but less UI) than Kibana can
Oct 25, 2016 15:36
You might have some mixup in the data inside the indices?
Oct 25, 2016 15:31
For the index one, you have 113227 undeleted documents. How many does Kibana say?
Oct 25, 2016 15:31
Or could the missing docs be null?
Oct 25, 2016 15:30
Are they populated in every document?
Oct 25, 2016 15:30
Or, you can turn time-based indexing off in Kibana
Oct 25, 2016 15:30
An index should only have time-based or non-time based documents in it, if you want to be able to browse it in Kibana. Otherwise Kibana will skip the documents that it can't determine the time for.
Oct 25, 2016 15:29
There is, but you can't mix time and not-time based documents in one index pattern
Oct 25, 2016 15:29
Create an index pattern that matches one of your indexes exactly (e.g. one) and see how you go with that
Oct 25, 2016 15:28
You caught me at a good time. I'm doing some maintenance on some of our Elastic indexes that have about a billion documents per index, so I have some time to spare
Oct 25, 2016 15:27
I would suggest creating a few different index patterns: one, two and three. Look inside each index and see if Kibana gives you accurate hit counts there
Oct 25, 2016 15:27
Hi
Oct 25, 2016 15:27
That's... not how Kibana is meant to be used. Do you actually have any time-based fields in your data?
Oct 25, 2016 15:27
You don't have date-based indexes, so I don't have enough information to tell you exactly, but my guess is that there is something being excluded by your Kibana range. Maybe you are filtering on a specific document type, or there is data outside of your date range that you're not expecting.
Oct 25, 2016 15:27
You haven't told us what the differences is though. How many hits is Kibana showing you?
Oct 25, 2016 15:27
How about you give us some more detail - tell us how different the hits and docs are. You're also probably better off querying http://127.0.0.1:9200/_stats/docs?pretty, as that gives you much more detail about the kinds of documents (primary, total, deleted). Does your Kibana index pattern match the index names correctly? Are you indexing daily/monthly/weekly/just one big index?
 
Sep 14, 2016 09:16
-1: Listen it's funny and all to go around saying "drop bears don't exist" but next time you're up at the Daintree rainforest and someone gets hurt because they read some tomfoolery here, don't say I didn't warn you. Irresponsible answer.
5
 
Jul 2, 2016 19:20
@RyanIG that doesn't tell me which processor it is. There are multiple Xeons that match that limited spec. Got an actual model number?
Jul 2, 2016 19:20
Honestly, just a guess, you've probably run out of PCI-e lanes. You don't mention which exact Xeon you've got so I'm going to guess a grand total of 40 lanes to be shared across everything. The cards probably don't operate below, say, 4 lanes so you may just be at the limits of what you can do. Just a guess.
 

 The Comms Room

ServerFault's lobby
Oct 30, 2015 13:51
I did try to reverse engineer the protocol that the built-in broker monitor used but I never had any luck. It's not published and I couldn't get it even with an NDA
Oct 30, 2015 13:51
And for our own servers, like I said we had our own monitor that was a thousand times better than the Magic one
Oct 30, 2015 13:50
And thats when our customer was "fuck no"
Oct 30, 2015 13:50
No wait, we already did the test environment and Magic asked if they could try it on the live environment
Oct 30, 2015 13:50
When I left we were meant to be building a test environment for them to remote into to test it, but our client was like "oh hella no"
Oct 30, 2015 13:49
But of course... it didn't
Oct 30, 2015 13:49
And it was meant to magically work
Oct 30, 2015 13:48
Restart the broker
Oct 30, 2015 13:48
Once the broker was installed you needed to enable SNMP in the mgrb.ini
Oct 30, 2015 13:48
If memory serves correct, you had to install the SNMP Windows service, then install the broker, which would give you the snmp.dll
Oct 30, 2015 13:47
Which is why I used to fall back to the usergroup
Oct 30, 2015 13:47
Our Magic distributor was in New Zealand and we were in Australia and of course Magic is in Israel so any troubleshooting we did needed to coordinate all three parties which was a nightmare
Oct 30, 2015 13:46
I've only ever met others at conferences and whatnot