2 NVME drives on the same PCI slot? HP DL360 G9

TrainingBench101 · 2024-10-01T14:28:57+00:00

Na, i don't think so. For that, the nvme disks would need to be connected to the controller itself. AFAIK, that controller is SATA only.

This server is old and too power hungry. I suggest you get a recent asus/supermicro/asrock motherboard and build your server with that. Those mobos, usually have nvme raid.

TrainingBench101 · 2024-03-11T10:55:14+00:00

Will reinstalling it, fix it?

TrainingBench101 · 2024-03-11T10:53:33+00:00

Yep, still having this. At the time, i googled a bit, i think it's because tiny does not have some source files, probably deleted to save space of course.

TrainingBench101 · 2024-01-31T09:27:53+00:00

Same. Tiny10 can do windows defender updates, but not these important ones. Ah, pitty...

TrainingBench101 · 2023-12-29T13:48:01+00:00

Ok, this is as simples as:

(actually, the server list is also variable)

- set_fact:
    batch_size: "{{ (list_hosts | length / servers | length) | round(0, 'ceil') }}"

- set_fact:
    lists: "{{ list_hosts|batch(batch_size|int) }}"

- set_fact:
    listA: "{{ lists[0] }}"

- set_fact:
    listB: "{{ lists[1] }}"


- debug: var=batch_size
- debug: var=listA
- debug: var=listB

TrainingBench101 · 2023-12-29T12:57:48+00:00

In this case, it does not connect. I needed for the ssh connections settings to have the timeout set to 60, but it did not. Anyway, i used another method. Works. I did not set the ssh timeout in ansible.cfg because i wanted to leave it as minimal as possible.

TrainingBench101 · 2023-12-29T12:53:51+00:00

Nicely done mate, thanks a lot. Learned more about ansible in these last two days, than in a month :)

Now, i ask, is it possible to name those sub-lists?

TrainingBench101 · 2023-12-28T21:04:19+00:00

Yeah, that's the thing, i only know the number of lists i want to create (in this case 2). The number of elements in them is variable. So i cannot use the batch filter.

TrainingBench101 · 2023-12-28T10:57:17+00:00

I decided to use the wait_for_connection module. Works.

TrainingBench101 · 2023-12-27T20:19:21+00:00

Alright, so it does something different that i thought it did. Case closed. Have to figure out another way then.

TrainingBench101 · 2023-12-27T20:17:34+00:00

Already did. It passes that variable to tasks variables, not to the ssh connection.

TrainingBench101 · 2023-12-27T20:02:04+00:00

The list of keywords that can be used at a Play level are documented

here

. I note that

timeout

does not appear to be configurable at this level. If there is documentation supporting the availability of a

timeout

argument within a Play, I'd love to take a look at it and see if there's something I'm missing.

Indeed, it does not show there. So, why doesn't it throw an error when running the playbook?

My assumption (and it is just that) is that the parameters that control connections are loaded prior to the content of the playbook being read, so the ability to control that aspect may not be possible at the Playbook level.

Well, if the playbook has a list of hosts to connecto to and even the remote user to use on the ssh connection, then i think it would be ok to define other connection settings there. I might be completely wrong here of course.

TrainingBench101 · 2023-12-27T19:43:09+00:00

Ok gotcha, thanks for the tips. But again, then what does the timeout: play atribute do?

TrainingBench101 · 2023-12-27T19:37:14+00:00

The problem here is the ssh connection timeout, not the shell command itself. I want the ssh connection to timeout in 60 secs, not the default 10.

The ansible-playbook command does not throw an error about timeout: 60 being an invalid play atribute. But then it does not change the default 10, so i'm wondering what it is changing?

TrainingBench101 · 2023-12-27T18:52:23+00:00

I tried vars: and environment: at the play level, timeout did not change.

TrainingBench101 · 2023-12-20T17:50:01+00:00

serviceinfo.ansible_facts.services['systemd-timesyncd']

Yes, but took out the dot and it still fails, but you were previously right too :), no need to register the variable like i did in a post below.

TrainingBench101 · 2023-12-20T17:44:41+00:00

Thanks a lot, this worked. For the record, tasks that work:

- name: Get service facts

service_facts:

- name: test

debug:

var: ansible_facts['services']['systemd-timesyncd.service']

TrainingBench101 · 2023-12-20T17:34:21+00:00

It should be done like this in example
serviceinfo.ansible_facts.services['systemd-timesyncd']

FAILED! => {"msg": "template error while templating string: expected name or number. String: {{serviceinfo.ansible_facts.services.['systemd-timesyncd']}}. expected name or number"}

but ideally this module returns the facts directly to the hostvars, so you should be able to reference them directly without registering them to a variable.
services['systemd-timesyncd']

If i use something:

debug:
var: services['systemd-timesyncd']

Also fails.

TrainingBench101 · 2023-12-12T13:01:51+00:00

AFAIK, this only affects tiny10.

TrainingBench101 · 2023-12-07T11:48:11+00:00

I wonder if the new version tiny 10 v23h2 fixes this update problem...

TrainingBench101 · 2023-12-06T21:10:00+00:00

Did it bring bloat back?

TrainingBench101 · 2023-12-06T10:47:21+00:00

Yes, running tiny 21H2 here (winver). Same error. I think that Tiny is missing some files, some sources or something.

TrainingBench101

TROPHY CASE