search for: 418a

...9; # yum install passenger Loaded plugins: fastestmirror passenger/7/x86_64/signature | 836 B 00:00:00 Retrieving key from https://packagecloud.io/gpg.key Importing GPG key 0xD59097AB: Userid : "packagecloud ops (production key) <ops at packagecloud.io>" Fingerprint: 418a 7f2f b0e1 e6e7 eabf 6fe8 c2e7 3424 d590 97ab From : https://packagecloud.io/gpg.key When I do it from a script, it fails. Regards, Yuri

Hi, Sorry for asking it again. I just thought I asked the question the wrong way. Too much unnecessary details. And therefore, got no replies. I'm configuring a server from, say, a script (automatically). I need it to be done without user saying, "Yes, it's okay to import the key." I was told to run the following command: yum makecache -y --disablerepo=*

...aded plugins: fastestmirror > passenger/7/x86_64/signature > | 836 B 00:00:00 > Retrieving key from https://packagecloud.io/gpg.key > Importing GPG key 0xD59097AB: > Userid : "packagecloud ops (production key) <ops at packagecloud.io>" > Fingerprint: 418a 7f2f b0e1 e6e7 eabf 6fe8 c2e7 3424 d590 97ab > From : https://packagecloud.io/gpg.key > > When I do it from a script, it fails. > > Regards, > Yuri It looks like the passenger RPM has a script importing the GPG key. Check using "rpm -q --scripts passenger". Is t...

...of importing key I choose (1 or 2). If I then ssh to container and run `yum install nginx` manually, it says: Retrieving key from https://packagecloud.io/gpg.key Importing GPG key 0xD59097AB: Userid : "packagecloud ops (production key) <ops at packagecloud.io>" Fingerprint: 418a 7f2f b0e1 e6e7 eabf 6fe8 c2e7 3424 d590 97ab From : https://packagecloud.io/gpg.key Is this ok [y/N]: And I suppose this extra confirmation request is what makes ansible fail. Can it be confirmed automatically? I tried to make it clear for those who don't use ansible, but feel free to...

...st: (extended_dn_out_ldb)->search ldb: ldb_trace_next_request: (show_deleted)->search ldb: ldb_trace_next_request: (partition)->search ldb: partition_request() -> (metadata partition) ldb: ldb_trace_next_request: (tdb)->search ldb: ldb_trace_response: ENTRY dn: <GUID=314022f9-1f59-418a-a1d2-7ada0f2f6e60>;<SID=S-1-5-21-98486140-92642785-846719952-1283>;CN=??????????? ?????????,OU=IT,OU=Departments,DC=klin,DC=kifato-mk,DC=com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user displayName:: 0KLQtdGF0L3QuNGH0LXRgdC60LDRjyDQv9C+0LTQtNC10Y...

On 2017-04-20 18:38, Rowland Penny wrote: > On Thu, 20 Apr 2017 18:00:24 +0200 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> On 2017-04-07 13:44, Sven Schwedas via samba wrote: >>> In the end I just upgraded all DCs to 4.5 and remote-deleted the >>> broken ones. Seemed to work without a hitch, manual removal was >>> only necessary

Situation: Trying to upgrade Samba from 4.1 to 4.5 without disruption too much by adding new DCs and demoting old ones. After bringing online the first 4.5 DC, I ran `demote --remove-other-dead-server=` on that DC to remove one of the old 4.1 DCs (held no FSMO roles). That seemed to run fine (the DC had been offline for a few weeks at that point and I didn't want to restore it just for

...1_AB1F_D472B7CB9017'" 0x9bd624 trace:msi:MSI_ParseSQL Parse returned 0 trace:msi:MSI_ViewExecute 0x173498 (nil) trace:msi:MSI_ViewFetch 0x173498 0x9bd628 trace:msi:msi_view_get_row 0x1598a8 0x174f60 0 0x9bd628 trace:msi:db_get_raw_stream L"\430b\4131\4735\3abe\44a7\4225\460c\45f6\4432\418a\4337\4472\47b6\38ce\3b05\3b83\3acc\397f\3b4f\47ca\3a44\384e\3abf\384b\47cf\390d\3887\39cb\3acc\3809\39c1" -> L"Binary.AdobeCustomActions.E35C3ECB_5FDA_49E1_AB1F_D472B7CB9017" trace:msi:MSI_ViewClose 0x173498 trace:msi:msiobj_release object 0x173498 destroyed trace:msi:msiobj_relea...