1. Почему отсутствует "Код-подпись для взаимодействия с сервером", из "коробки" я не понимаю, он же вроде как требуется по умолчанию в админке в настройках модуля Pus-n-Pull, не зависимо от того какой у нас Type сервера. По умолчанию в BitrixVM - Nginx-PushStreamModule , ну так а ключ где? Если я например не собираюсь (или не могу, по причине описанной ниже) переходить на NodeJS, то как мне ключ получить?. Как понять эту "логику" ?
2. Как все таки выполнить этот переход на NodeJS, у меня также падает задание в error
в логах задания BitrixVM (7.5.5) такое
| Код |
|---|
[root@vm1 ~]# cat /opt/webdir/temp/pushserver_5681310086/status
[WARNING]: Consider using the get_url or uri module rather than running
'curl'. If you need to use command because get_url or uri is insufficient you
can add 'warn: false' to this command task or set 'command_warnings=False' in
ansible.cfg to get rid of this message.
[WARNING]: Consider using the yum, dnf or zypper module rather than running
'rpm'. If you need to use command because yum, dnf or zypper is insufficient
you can add 'warn: false' to this command task or set 'command_warnings=False'
in ansible.cfg to get rid of this message.
[WARNING]: Consider using the yum module rather than running 'yum'. If you
need to use command because yum is insufficient you can add 'warn: false' to
this command task or set 'command_warnings=False' in ansible.cfg to get rid of
this message.
*************************************************
ok: [vm4] => (item=/etc/yum.repos.d/nodesource-el.repo)
ok: [vm4] => (item=/etc/yum.repos.d/nodesource-el6.repo)
TASK [push-server : configure nodejs repository] *******************************
changed: [vm4]
TASK [push-server : delete old nodejs-packages] ********************************
failed: [vm4] (item=nodejs) => {"changed": true, "cmd": "rpm -e --nodeps \"nodejs\"", "delta": "0:00:00.053947", "end": "2024-07-08 23:33:27.352412", "item": "nodejs",
"msg": "non-zero return code", "rc": 1, "start": "2024-07-08 23:33:27.298465", "stderr": "error: package nodejs is not installed", "stderr_lines": ["error: package no
dejs is not installed"], "stdout": "", "stdout_lines": []}
failed: [vm4] (item=npm) => {"changed": true, "cmd": "rpm -e --nodeps \"npm\"", "delta": "0:00:00.039297", "end": "2024-07-08 23:33:27.703592", "item": "npm", "msg": "
non-zero return code", "rc": 1, "start": "2024-07-08 23:33:27.664295", "stderr": "error: package npm is not installed", "stderr_lines": ["error: package npm is not ins
talled"], "stdout": "", "stdout_lines": []}
...ignoring
TASK [push-server : shell] *****************************************************
changed: [vm4]
TASK [push-server : install packages] ******************************************
fatal: [vm4]: FAILED! => {"changed": false, "msg": "Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was\n14
: curl#6 - \"Could not resolve host: mirrorlist.centos.org; Unknown error\"\n\n\n One of the configured repositories failed (Unknown),\n and yum doesn't have enough ca
ched data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n 1. Contact the upstream for the repos
itory and get them to fix the problem.\n\n 2. Reconfigure the baseurl/etc. for the repository, to point to a working\n upstream. This is most often useful i
f you are using a newer\n distribution release than is supported by the repository (and the\n packages for the previous distribution release still work).
\n\n 3. Run the command with the repository temporarily disabled\n yum --disablerepo=<repoid> ...\n\n 4. Disable the repository permanently, so yum
won't use it by default. Yum\n will then just ignore the repository until you permanently enable it\n again or use --enablerepo for temporary usage:\n\n
yum-config-manager --disable <repoid>\n or\n subscription-manager repos --disable=<repoid>\n\n 5. Configure the failing repository to
be skipped, if it is unavailable.\n Note that yum will try to contact the repo. when it runs most commands,\n so will have to try and fail each time (and
thus. yum will be be much\n slower). If it is a very temporary problem though, this is often a nice\n compromise:\n\n yum-config-manager --sa
ve --setopt=<repoid>.skip_if_unavailable=true\n\nCannot find a valid baseurl for repo: base/7/x86_64\n", "rc": 1, "results": []}
to retry, use: --limit @/etc/ansible/push-server.retry
PLAY RECAP *********************************************************************
vm4 : ok=10 changed=3 unreachable=0 failed=1
|
