Welcome to gattis.org!



posted Sep 27, 2018, 6:51 AM by Allen Gattis   [ updated Sep 27, 2018, 6:51 AM ]

NFS in fstab fails to mount at boot

posted Sep 7, 2018, 10:21 AM by Allen Gattis

Turns out that in Debian 9, NFS entries in the fstab don't come up at boot time. 

At boot, systemd autodetects that the type is NFS and _should_ wait for networking, but it doesn't and no amount of _netdev or other things seem to work.

Turns out to be the way the interface is presented from the network config file. Change the interface:
    allow-hotplug ens192
    auto ens192

The Clue:

No Help:

mount error(112): Host is down

posted Aug 31, 2018, 5:55 PM by Allen Gattis

If you get this in linux when mounting a windows 10 share, it's because you need to specify the SMB version

adduser: The --group, --ingroup, and --gid options are mutually exclusive.

posted May 5, 2018, 11:27 AM by Allen Gattis

You may go to create a service account with a known UID and GID like so:

sudo adduser --system --no-create-home --disabled-login --uid 112 --group --gid 117 some-service

However, that command can't be done on one line.

adduser: The --group, --ingroup, and --gid options are mutually exclusive.

You might be tempted to just omit the group. However, that command attempts to create a group if that matches the user id, and you may find you have more groups than users.

adduser: The GID 112 is already in use.

So make it a two-liner

sudo addgroup --gid 117 some-service
sudo adduser --system --no-create-home --disabled-login --uid 112 --gid 117 some-service

Dynamic Address Static DNS Order

posted Apr 7, 2017, 10:38 AM by Allen Gattis

By default, you can add name servers to your /etc/networking/interfaces file, but you'll still get the DHCP supplied ones first. To change that, you must supercede that in the /etc/resolv.conf options.


Unknown USB bridge

posted Feb 16, 2017, 10:01 AM by Allen Gattis   [ updated Mar 14, 2017, 5:12 AM ]

When checking a disk with smartmontools, you may get this 

allen@work:~$ sudo smartctl -a  /dev/sdc

/dev/sdc: Unknown USB bridge [0x0bc2:0xab28 (0x100)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

Check the page below and add the -d option.

allen@work:~$ sudo smartctl -d sat -a  /dev/sdc

Device Model:     ST4000LM016-1N2170
Serial Number:    W8009R7T
LU WWN Device Id: 5 000c50 08ba9a185
Firmware Version: 0002

If that fails, you may need to switch from the newer 'uac' usb driver back to the old one

HPDBA0235I The server lost the client's authentication

posted May 17, 2016, 1:17 PM by Allen Gattis

When configuring ISIM to talk to ISAM, you have to deploy and configure the Java Run Time. If you get the above exception when issuing the 

com.tivoli.pd.jcfg.SvrSslCfg it's likely because your local copy of PD.jar is out of date. 

The answer is to download the most recent pdjrte from the ISAM appliance and redeploy.


NXLOG Couldn't read next event

posted May 16, 2016, 6:34 AM by Allen Gattis   [ updated May 16, 2016, 6:37 AM ]

If you see this error message from nxlog:

ERROR Couldn't read next event, corrupted eventlog?; The data is invalid.

Congrats - you've hit a bug.


The work-around is to limit your log event subscriptions on the input side by using a query.  Example:

<Input in>
  Module im_msvistalog
  Query <QueryList><Query Id="0" Path="Microsoft-Windows-PrintService/Operational"><Select Path="Microsoft-Windows-PrintService/Operational">*</Select></Query></QueryList>
  Exec if $EventID != 307 drop();
  Exec $type = "IDWorks";

Kibana rounding to 16 significant digits

posted Apr 7, 2016, 10:00 AM by Allen Gattis   [ updated Apr 7, 2016, 10:01 AM ]

Turns out, if you have a value of type integer, that's just the limit. While elasticsearch shows you this:

curl http://localhost:9200/logstash-db-2016/isim-process/8163783564660983218?pretty
  "_index" : "logstash-db-2016",
  "_type" : "isim-process",
  "_id" : "8163783564660983218",
  "_version" : 1,
  "found" : true,
  "_source":{"requester_name":"8163783564660983218","request_num":8163783618037078861,"started":"2016-04-07 15:16:16:139 GMT","completed":"2016-04-07 15:16:16:282 GMT","subject_service":"Service","request_type":"EP","result_summary":"AA","requestee_name":"Mr. Requester","subject":"mrRequest","@version":"1","@timestamp":"2016-04-07T15:16:16.282Z"}

Kibana shows you this

View: Table / JSON / Raw

request_num  8163783618037079000

Looking at the JSON will give you the clue - it's being treated as an integer and not a string.

"_source": { "requester_name": "8163783564660983218", "request_num": 8163783618037079000, "started": "2016-04-07 15:16:16:139 GMT", "completed": "2016-04-07 15:16:16:282 GMT",

Mutate it to string in logstash to get your precision back.


Reset Chrome Magnet Link Handling

posted Feb 27, 2016, 10:42 AM by Allen Gattis   [ updated Feb 27, 2016, 10:43 AM ]

Picked the wrong thing when chrome first asked you, or chrome is just opening a new window on ubuntu? Have it ask you again by deleting the file that tells it what to do with external protocols 

rm  ~/.config/google-chrome/Local\ State

1-10 of 46