Техническая поддержка
Если вы не нашли ответ на свой вопрос, то обратитесь в техническую поддержку.
help@rvigroup.ru
Регистрация аккаунта в облаке P2P через Guarding Expert, Ошибка регистрации аккаунта в облаке P2P через Guarding Expert
|
click User Сообщений: 1 |
Добрый день! Пытаюсь зарегистрировать аккаунт в облаке P2P через Guarding Expert с разных компьютеров. После заполнения всех полей и ввода кода подтверждения из электронной почты, при попытке регистрации, получаю сообщение — «Неизвестная ошибка (CloudDataCenter [1001]). Регистрация не проходит. Помогите с решением проблемы регистрации. |
|
Павел Байков Administrator Сообщений: 2621 |
#2 09.07.2018 09:03:50 Добрый день. Попробуйте зарегистрироваться через официальный сайт облачного сервиса ezvizlife.com Для более оперативного решения возникшего вопроса вы можете позвонить по телефону горячей линии 8 (800) 700-16-61
|
Скачать:
Контакты технической поддержки:
- 8 (800) 775-77-00 (звонок по России бесплатный)
- 8 (800) 080-22-00 (звонок по Казахстану бесплатный)
- Связаться через онлайн-консультант (всплывающее меню слева)
- Для получения технической консультации Вы можете оставить запрос на форуме.
- Информацию по гарантии и порядке отправки оборудования в сервисный центр Вы можете получить разделе Сервиса и гарантии.
Перед обращением в техническую поддержку нужно уточнить модель устройства RVI, версию и дату прошивки.
⚠️ Before submitting, please verify the following: ⚠️
- This is a bug, not a question or a configuration issue.
- This issue is not already reported on Github (I’ve searched it).
- Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
- I agree to follow Nextcloud’s Code of Conduct
Bug description
When I try to sync the .vscode extension folder with the Nextcloud Client 3.6.4 (previous versions had the same problems) I get the messages unknown error and network error: 99. Then the Nextcloud Client is freezing and then crashing.
Steps to reproduce
- Install VS Code on Windows
- Install some extensions
- Try to sync the folder under C:Users%username%.vscode
Expected behavior
The sync should not fail.
Which files are affected by this bug
nearly all files
Operating system
Windows
Which version of the operating system you are running.
Windows 11 21H2
Package
Appimage
Nextcloud Server version
25.0.3
Nextcloud Desktop Client version
3.6.4
Is this bug present after an update or on a fresh install?
Fresh desktop client install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
- Default internal user-backend
- LDAP/ Active Directory
- SSO — SAML
- Other
Nextcloud Server logs
The logs are in the `debug.zip`, else I get this error when submitting this issue `There was an error creating your issue: body is too long (maximum is 65536 characters). `
Additional info
I’m using this Docker Compose file:
docker-compose.yml.txt
Here the client logs:
debug.zip
Nextcloud is behind a Haproxy, but I tried also with a direct connection to the Docker container. Same result.
Here some screenshots:
Поддерживаемые стандарты
Поддерживаемые стандарты
Аналог 960H
8
IP 1 Mpix (720p)
2
IP 2 Mpix (1080p)
1
Видео / Аудио
Видео / Аудио
Особенности видеовыходов
1 x BNC (704×576)
1 x VGA (1920×1080)
1 x HDMI (1920×1080)
Формат записи видео / аудио
H.264 / G.711u
Вывод на экран
Деление 1/4/6/8/9/16 каналов, зум, переключение каналов, скрытие камеры
Настройка выхода (стандарт, светлый, мягкий, яркий
Видеовход
8 x BNC, 1.0В p-p, 75Ом (PAL/NTSC)
Живое видео
8 x 960H (960×576) 30к/с + IP 1080p (1920×1080) 30к/с + IP 720p (1920×1080) 30к/с
Видеовыход
1 x HDMI | 1 x VGA | 1 x BNC
Запись
8 х 960H (960×576) 30к/с / D1 (704х576) 30к/с / HD1 (704х288) 30к/с / CIF (352×288) 30к/с + IP 1080p (1920×1080) 30 к/с + IP 720p (1280×720) 30к/с
Воспроизведение
1 x 1080p 30к/с + 1 x 720р 30к/с
6 х 960H 30к/с
Сеть
8 x 960H (960×576) 30к/с + IP 1080p (1920×1080) 30к/с + IP 720p (1920×1080) 30к/с
Аудиовход
1 x RCA
Режимы записи
Ручной
По расписанию
По тревоге / По движению (Предзапись 0-30 с, Постзапись 5-600 с)
Аудиовыход
1 x RCA
Настройки каналов
Независимые для каждого: параметры записи, настройки детектора движения, маскировка области (4 зоны), цвет изображения (два интервала работы), отображение имени, даты
Объём записи на канал
6 Мбит — 63 Гб/сутки
4 Мбит — 42 Гб/сутки
1 Мбит — 11 Гб/сутки
128 Кбит — 1.32 Гб/сутки
32 Кбит — 0.33 Гб/сутки
(указан максимум, фактический зависит от скорости и качества записи)
Поиск
По дате/времени
По событию
По меткам
Режимы воспроизведения
Вперёд и назад / Нормальное / Покадровое / Замедленное (х1/2, х1/4, х1/8) / ускоренное (х2, х4, х8, х16)
Интерфейсы
Интерфейсы
SATA
1 x SATA 3,5″ до 6Тб:
HDD — основное хранение данных / S.M.A.R.T. / инфо: статус, общая ёмкость, доступная ёмкость
USB
2 x USB 2.0:
Flash — архивирование обновление ПО, конфигурация / инфо: статус, ёмкость
Мышь — управление видеорегистратором (в комплекте)
3G модем (Huawei E173) — интернет
RS-485
—
RS-232
—
ИК порт
—
Система
Система
Процессор
HiSilicon Hi3521
Производительность
Мультиплекс (одновременно: живое видео, запись, воспроизведение, сеть, архивирование, меню)
Операционная система
Интегрированная OS Linux
Графический интерфейс
Русифицирован. Основное, всплывающее и быстрое меню
Ограничение доступа
Администратор + Пользователь (установка прав доступа, ручная блокировка)
Журнал событий
Указание канала, даты и времени начала и окончания события
Тревога
Тревога
Действие
Вывод изображения на монитор / Сигнал / Уведомление центру наблюдения / Уведомление по email (картинка)
Условия срабатывания
Потеря видео / детекция движения (7 уровней, 396 зон) / закрытие камеры (3 уровня) / системный сбой
Сеть
Сеть
Порт RJ45
1 x 10/100 Мбит (ONVIF 2.2, HTTP, SMTP, UPnP, RTSP, FTP, DDNS, DHCP, PPPOE, NAT, P2P)
Битрейт на канал
32 Кбит — 3 Мбит
WEB браузер
IE (Windows 10 / 8 / 7 / VISTA / XP)
CMS программа
iVMS 4.1 (Windows 10 / 8 / 7 / VISTA / XP) — 64 канала на экран
Мобильный клиент
iVMS 4.5 (Android, iPhone)
Облачный сервис
Cloud Р2Р:
iVMS 4.1, WEB интерфейс — hicloudcam.com (Windows 10 / 8 / 7 / VISTA / XP)
iVMS 4.5, ezviz (Android / iPhone / iPad)
Физические параметры
Физические параметры
Активное охлаждение
Отсутствует
Температурный режим
-10°C ~ +55°C
Размер (ШxВxГ)
200x45x200 мм
Питание
Постоянное 12В 1.5А, внешний адаптер 100~240В, 50/60Гц (в комплекте)
Комплектация
1. Видеорегистратор — 1 шт.
2. Адаптер питания — 1 шт.
3. USB мышь — 1 шт.
4. Краткое руководство пользователя — 1 шт.
5. CD диск с ПО и инструкциями — 1 шт.
6. Кабель данных SATA — 1 шт.
7. Кабель питания HDD — 1 шт.
8. Крепёжный комплект — 1 шт.
Информация о технических характеристиках, комплекте поставки и внешнем виде товара носит справочный характер и не является публичной офертой.
| Code | Reason |
| 0 | No error |
| 1 | User-initiated client disconnect. |
| 2 | User-initiated client logoff. |
| 3 | Your Remote Desktop Services session has ended, possibly for one of the following reasons: The administrator has ended the session. An error occurred while the connection was being established. A network problem occurred. For help solving the problem, see «Remote Desktop» in Help and Support. |
| 260 | Remote Desktop can’t find the computer «». This might mean that «» does not belong to the specified network. Verify the computer name and domain that you are trying to connect to. |
| 262 | This computer can’t connect to the remote computer. Your computer does not have enough virtual memory available. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 264 | This computer can’t connect to the remote computer. The two computers couldn’t connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 266 | The smart card service is not running. Please start the smart card service and try again. |
| 516 | Remote Desktop can’t connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. |
| 522 | A smart card reader was not detected. Please attach a smart card reader and try again. |
| 772 | This computer can’t connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 778 | There is no card inserted in the smart card reader. Please insert your smart card and try again. |
| 1030 | Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again. |
| 1032 | The specified computer name contains invalid characters. Please verify the name and try again. |
| 1034 | An error has occurred in the smart card subsystem. Please contact your helpdesk about this error. |
| 1796 | This computer can’t connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 1800 | Your computer could not connect to another console session on the remote computer because you already have a console session in progress. |
| 2056 | The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator. |
| 2308 | Your Remote Desktop Services session has ended. The connection to the remote computer was lost, possibly due to network connectivity problems. Try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support. |
| 2311 | The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2312 | A licensing error occurred while the client was attempting to connect (Licensing timed out). Please try connecting to the remote computer again. |
| 2567 | The specified username does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support. |
| 2820 | This computer can’t connect to the remote computer. An error occurred that prevented the connection. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2822 | Because of an error in data encryption, this session will end. Please try connecting to the remote computer again. |
| 2823 | The user account is currently disabled and cannot be used. For assistance, contact your system administrator or technical support. |
| 2825 | The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support. |
| 3079 | A user account restriction (for example, a time-of-day restriction) is preventing you from logging on. For assistance, contact your system administrator or technical support. |
| 3080 | The remote session was disconnected because of a decompression failure at the client side. Please try connecting to the remote computer again. |
| 3335 | As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support. |
| 3337 | The security policy of your computer requires you to type a password on the Windows Security dialog box. However, the remote computer you want to connect to cannot recognize credentials supplied using the Windows Security dialog box. For assistance, contact your system administrator or technical support. |
| 3590 | The client can’t connect because it doesn’t support FIPS encryption level. Please lower the server side required security level Policy, or contact your network administrator for assistance |
| 3591 | This user account has expired. For assistance, contact your system administrator or technical support. |
| 3592 | Failed to reconnect to your remote session. Please try to connect again. |
| 3593 | The remote PC doesn’t support Restricted Administration mode. |
| 3847 | This user account’s password has expired. The password must change in order to logon. Please update the password or contact your system administrator or technical support. |
| 3848 | A connection will not be made because credentials may not be sent to the remote computer. For assistance, contact your system administrator. |
| 4103 | The system administrator has restricted the times during which you may log in. Try logging in later. If the problem continues, contact your system administrator or technical support. |
| 4104 | The remote session was disconnected because your computer is running low on video resources. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 4359 | The system administrator has limited the computers you can log on with. Try logging on at a different computer. If the problem continues, contact your system administrator or technical support. |
| 4615 | You must change your password before logging on the first time. Please update your password or contact your system administrator or technical support. |
| 4871 | The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contact your system administrator or technical support. |
| 5127 | The Kerberos sub-protocol User2User is required. For assistance, contact your system administrator or technical support. |
| 6919 | Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid. In some cases, this error might also be caused by a large time discrepancy between the client and server computers. |
| 7431 | Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer. Make sure your computer’s clock is set to the correct time, and then try connecting again. If the problem occurs again, contact your network administrator or the owner of the remote computer. |
| 8711 | Your computer can’t connect to the remote computer because your smart card is locked out. Contact your network administrator about unlocking your smart card or resetting your PIN. |
| 9479 | Could not auto-reconnect to your applications,please re-launch your applications |
| 9732 | Client and server versions do not match. Please upgrade your client software and then try connecting again. |
| 33554433 | Failed to reconnect to the remote program. Please restart the remote program. |
| 33554434 | The remote computer does not support RemoteApp. For assistance, contact your system administrator. |
| 50331649 | Your computer can’t connect to the remote computer because the username or password is not valid. Type a valid user name and password. |
| 50331650 | Your computer can’t connect to the remote computer because it can’t verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331651 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) The requested Remote Desktop Gateway server address and the server SSL certificate subject name do not match. 2) The certificate is expired or revoked. 3) The certificate root authority does not trust the certificate. Contact your network administrator for assistance. |
| 50331652 | Your computer can’t connect to the remote computer because the SSL certificate was revoked by the certification authority. Contact your network administrator for assistance. |
| 50331653 | This computer can’t verify the identity of the RD Gateway «». It’s not safe to connect to servers that can’t be identified. Contact your network administrator for assistance. |
| 50331654 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address requested and the certificate subject name do not match. Contact your network administrator for assistance. |
| 50331655 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server’s certificate has expired or has been revoked. Contact your network administrator for assistance. |
| 50331656 | Your computer can’t connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance. |
| 50331657 | An error occurred while sending data to the Remote Desktop Gateway server. The server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331658 | An error occurred while receiving data from the Remote Desktop Gateway server. Either the server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331659 | Your computer can’t connect to the remote computer because an alternate logon method is required. Contact your network administrator for assistance. |
| 50331660 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address. |
| 50331661 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331662 | Your computer can’t connect to the remote computer because the Remote Desktop Services client component is missing or is an incorrect version. Verify that setup was completed successfully, and then try reconnecting later. |
| 50331663 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is running low on server resources and is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331664 | Your computer can’t connect to the remote computer because an incorrect version of rpcrt4.dll has been detected. Verify that all components for Remote Desktop Gateway client were installed correctly. |
| 50331665 | Your computer can’t connect to the remote computer because no smart card service is installed. Install a smart card service and then try again, or contact your network administrator for assistance. |
| 50331666 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Try again using a valid smart card, or contact your network administrator for assistance. |
| 50331667 | Your computer can’t connect to the remote computer because no smart card is available. Try again using a smart card. |
| 50331668 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Reinsert the smart card and then try again. |
| 50331669 | Your computer can’t connect to the remote computer because the user name or password is not valid. Please type a valid user name and password. |
| 50331671 | Your computer can’t connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance. |
| 50331672 | The Remote Desktop Gateway server has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331673 | The Remote Desktop Gateway server administrator has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331674 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) Your credentials (the combination of user name, domain, and password) were incorrect. 2) Your smart card was not recognized. |
| 50331675 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not listed in the RD Gateway’s permission list 2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting an FQDN or IP address format (for example, computer1.fabrikam.com or 157.60.0.1). Contact your network administrator for assistance. |
| 50331676 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not authorized to access the RD Gateway «» 2) Your computer is not authorized to access the RD Gateway «» 3) You are using an incompatible authentication method (for example, the RD Gateway might be expecting a smart card but you provided a password) Contact your network administrator for assistance. |
| 50331679 | Your computer can’t connect to the remote computer because your network administrator has restricted access to this RD Gateway server. Contact your network administrator for assistance. |
| 50331680 | Your computer can’t connect to the remote computer because the web proxy server requires authentication. To allow unauthenticated traffic to an RD Gateway server through your web proxy server, contact your network administrator. |
| 50331681 | Your computer can’t connect to the remote computer because your password has expired or you must change the password. Please change the password or contact your network administrator or technical support for assistance. |
| 50331682 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance. |
| 50331683 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server does not support the request. Contact your network administrator for assistance. |
| 50331684 | Your computer can’t connect to the remote computer because the client does not support one of the Remote Desktop Gateway’s capabilities. Contact your network administrator for assistance. |
| 50331685 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server and this computer are incompatible. Contact your network administrator for assistance. |
| 50331686 | Your computer can’t connect to the remote computer because the credentials used are not valid. Insert a valid smart card and type a PIN or password, and then try connecting again. |
| 50331687 | Your computer can’t connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331688 | Your computer can’t connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331689 | Your computer can’t connect to the remote computer because the RD Gateway server that you are trying to connect to is not allowed by your computer administrator. If you are the administrator, add this Remote Desktop Gateway server name to the trusted Remote Desktop Gateway server list on your computer and then try connecting again. |
| 50331690 | Your computer can’t connect to the remote computer because your computer or device did not meet the Network Access Protection requirements set by your network administrator, for one of the following reasons: 1) The Remote Desktop Gateway server name and the server’s public key certificate subject name do not match. 2) The certificate has expired or has been revoked. 3) The certificate root authority does not trust the certificate. 4) The certificate key extension does not support encryption. 5) Your computer cannot verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331691 | Your computer can’t connect to the remote computer because a user name and password are required to authenticate to the Remote Desktop Gateway server instead of smart card credentials. |
| 50331692 | Your computer can’t connect to the remote computer because smart card credentials are required to authenticate to the Remote Desktop Gateway server instead of a user name and password. |
| 50331693 | Your computer can’t connect to the remote computer because no smart card reader is detected. Connect a smart card reader and then try again, or contact your network administrator for assistance. |
| 50331695 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to missing firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331696 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to invalid firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331698 | Your Remote Desktop Services session ended because the remote computer didn’t receive any input from you. |
| 50331699 | The connection has been disconnected because the session timeout limit was reached. |
| 50331700 | Your computer can’t connect to the remote computer because an invalid cookie was sent to the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331701 | Your computer can’t connect to the remote computer because the cookie was rejected by the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331703 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is expecting an authentication method different from the one attempted. Contact your network administrator for assistance. |
| 50331704 | The RD Gateway connection ended because periodic user authentication failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331705 | The RD Gateway connection ended because periodic user authorization failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331707 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway and the remote computer are unable to exchange policies. This could happen due to one of the following reasons: 1. The remote computer is not capable of exchanging policies with the Remote Desktop Gateway. 2. The remote computer’s configuration does not permit a new connection. 3. The connection between the Remote Desktop Gateway and the remote computer ended. Contact your network administrator for assistance. |
| 50331708 | Your computer can’t connect to the remote computer, possibly because the smart card is not valid, the smart card certificate was not found in the certificate store, or the Certificate Propagation service is not running. Contact your network administrator for assistance. |
| 50331709 | To use this program or computer, first log on to the following website: <a href=»»></a>. |
| 50331710 | To use this program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331711 | Your session has ended. To continue using the program or computer, first log on to the following website: <a href=»»></a>. |
| 50331712 | Your session has ended. To continue using the program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331713 | The RD Gateway connection ended because periodic user authorization failed. Your computer or device didn’t pass the Network Access Protection (NAP) requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331714 | Your computer can’t connect to the remote computer because the size of the cookie exceeded the supported size. Contact your network administrator for assistance. |
| 50331716 | Your computer can’t connect to the remote computer using the specified forward proxy configuration. Contact your network administrator for assistance. |
| 50331717 | This computer cannot connect to the remote resource because you do not have permission to this resource. Contact your network administrator for assistance. |
| 50331718 | There are currently no resources available to connect to. Retry the connection or contact your network administrator. |
| 50331719 | An error occurred while Remote Desktop Connection was accessing this resource. Retry the connection or contact your system administrator. |
| 50331721 | Your Remote Desktop Client needs to be updated to the newest version. Contact your system administrator for help installing the update, and then try again. |
| 50331722 | Your network configuration doesn’t allow the necessary HTTPS ports. Contact your network administrator for help allowing those ports or disabling the web proxy, and then try connecting again. |
| 50331723 | We’re setting up more resources, and it might take a few minutes. Please try again later. |
| 50331724 | The user name you entered does not match the user name used to subscribe to your applications. If you wish to sign in as a different user please choose Sign Out from the Home menu. |
| 50331725 | Looks like there are too many users trying out the Azure RemoteApp service at the moment. Please wait a few minutes and then try again. |
| 50331726 | Maximum user limit has been reached. Please contact your administrator for further assistance. |
| 50331727 | Your trial period for Azure RemoteApp has expired. Ask your admin or tech support for help. |
| 50331728 | You no longer have access to Azure RemoteApp. Ask your admin or tech support for help. |
Platform Notice: Data Center Only — This article only applies to Atlassian products on the data center platform.
When upgrading Confluence Data Center to 6.10 or later, the following error appears in the application log:
ERROR [localhost-startStop-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$saveSharedProperty$3 Could not save access.mode into the shared confluence.cfg.xml file: {}
com.atlassian.config.ConfigurationException: failed to find config at: shared-home/confluence.cfg.xml
...
Caused by: java.io.FileNotFoundException: shared-home/confluence.cfg.xml (No such file or directory)Read-only mode, introduced in Confluence 6.10, writes the access mode (whether the site is currently read only or read / write) to the confluence.cfg.xml file located in the shared home directory.
If you installed Confluence Data Center prior to Confluence 6.1, this file will not be present in your shared home directory, as it was only created for new installs, not when you upgraded to Confluence 6.1 or later.
The simplest way to resolve this issue is to create the confluence.cfg.xml file in your shared home directory:
- Copy the
confluence.cfg.xmlfile from the local home directory on one of your Confluence nodes to your shared home directory. -
Edit the file, and remove all properties, except for the following:
<confluence-configuration> <setupStep>complete</setupStep> <setupType>cluster</setupType> <buildNumber>7801</buildNumber> <properties> <property name="access.mode"> ... </property> <property name="atlassian.license.message"> ... </property> <property name="confluence.cluster">true</property> <property name="hibernate.setup">true</property> <property name="jwt.private.key"> ... </property> <property name="jwt.public.key"> ... </property> <property name="lucene.index.dir">${localHome}index</property> </properties> </confluence-configuration>Make sure you include the real values for each parameter and property, for example the build number, and your private and public key. We’ve omitted the license and keys here to make this example easier to read.
-
Save the file, then start Confluence.
| Саша | #0 23.10.2020 |
 Сообщений: 17 Пользователь 2 |
После обновления CloudKey до актуальной прошивки. Контроллер перезагрузился, по IP дает зайти к себе на веб интерфейс, после ввода логина и пароля уходит в пустую страницу. |
При работе в Nextcloud возникают ошибки.
Для их устранения необходимо перевести облачное хранилище в режим обслуживания. Сделаем это с помощью утилиты occ находящаяся в корне web-проекта.
Переводим в режим обслуживания выполнив команду:
# sudo -u www-data php occ maintenance:mode --on
Для отключения режима обслуживания выполним команду:
# sudo -u www-data php occ maintenance:mode --off
В режиме обслуживания на Desktop-клиентах будет запрошен пароль пользователя.
Ошибка «File is locked»
Ошибка при использовании серверов с медленной дисковой подсистемой.
Для исправления потребует перевести хранилища в режим обслуживания и выполненить SQL-запрос по очистке таблицы блокировок.
> delete from oc_file_locks;
Ошибка «Файл был удален с сервера» («File was deleted from server»)
Это довольно распространенная не блокирующая ошибка и синхронизация будет продолжаться, но в логах клиента будут присутствовать соответствующие ошибки.
Для устранения этой ошибки необходимо воспользоваться встроенной функцией сканирования файлового хранилища. Эта функция может быть запущена для всех пользователей:
# sudo -u www-data php occ files:scan --all
Это доволно длительная операция и зависящая от того сколько пользователей и файлов и для устранения проблем у одного пользователя можно указать вместо параметра его имя или идентификатор из Active Directory:
# sudo -u www-data php occ files:scan 2718B513-40C2-497A-8461-5CA930CEC4E9
Если вам известно расположение сбойного файла, то можно указать какой каталог требуется пересканировать:
# sudo -u www-data php occ files:scan 2718B513-40C2-497A-8461-5CA930CEC4E9 --path="2718B513-40C2-497A-8461-5CA930CEC4E9/files_versions/"
Когда штатные средства не помогают, придется удалить записи о файлах напрямую из базы данных, подключаемся базе данных mysql и выполняем запрос файлового идентификатора искомого файла.
> select fileid,path from oc_filecache where path like '%data/4.%';
Где, ‘%data/4.%’ — это запрос части имени файла вызывающего ошибку.
Следующим этапом удаляем идентификаторы сбойных файлов:
> delete from oc_filecache where fileid=589434;
589434 — соответственно идентификатор сбойного файла.
Ошибка «Precondition failed (An If-Match header was specified and the resource did not exist)»
Ошибка возникает на стороне клиента и оптимальным решением является переместить файл на временное хранение в другой каталог и после окончания синхронизации переместить файл обратно.
Cannot start up WebLogic and NodeManager after Oracle Cloud data center outage
Problem
When starting Oracle WebLogic Server 11g AdminServer on an Oracle Cloud Infrastructure virtual machine, the WebLogic process was dying at startup. No explanation whatsoever as shown here:
INFO: Notification sent for Mapping config object reloaded
<Jul 16, 2018, 8:20:01,49 PM EDT> <Warning> <JMX> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminhost.raastech.com:7002/jndi/weblogic.management.mbeanservers.editsession.DOMAIN.ServiceBus.>
<Jul 16, 2018, 8:20:01,73 PM EDT> <Warning> <JMX> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminhost.raastech.com:7002/jndi/weblogic.management.mbeanservers.edit.>
<Jul 16, 2018, 8:20:01,147 PM EDT> <Warning> <JMX> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminhost.raastech.com:7002/jndi/weblogic.management.mbeanservers.domainruntime.>
Jul 16, 2018 8:20:01 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: Notification sent for Mapping config object reloaded /u01/app/oracle/middleware/products/fmw1221/user_projects/domains/soa_domain/bin/startWebLogic.sh: line 203: 24671 Killed ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WLS_POLICY_FILE} ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}
Stopping Derby server…
Derby server stopped.
When starting up NodeManager, observed the following errors:
<Jul 16, 2018 8:21:11 PM EDT> <SEVERE> <Fatal error in NodeManager server>
java.io.IOException: The server is unable to create a server socket for listening. The address soahost1.raastech.com might be incorrect or another process is using port 5556: java.net.BindException: Cannot assign requested address
at weblogic.nodemanager.server.NMServer.start(NMServer.java:351)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:529)
at weblogic.NodeManager.main(NodeManager.java:31)
Caused by: java.net.BindException: Cannot assign requested address
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at java.net.ServerSocket.<init>(ServerSocket.java:237)
at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:181)
at sun.security.ssl.SSLServerSocketImpl.<init>(SSLServerSocketImpl.java:140)
at sun.security.ssl.SSLServerSocketFactoryImpl.createServerSocket(SSLServerSocketFactoryImpl.java:95)
at weblogic.nodemanager.server.SSLListener.privilegedInit(SSLListener.java:134)
at weblogic.nodemanager.server.SSLListener.access$000(SSLListener.java:33)
at weblogic.nodemanager.server.SSLListener$1.run(SSLListener.java:97)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:94)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:349)
… 2 more
Failed attempts at resolution:
- Started WebLogic manually. No help.
- Increased debugging. No additional information.
- Reset the ‘weblogic’ password. No help.
- Cleared the ~/tmp ~/cache ~/data folders of the AdminServer. No help.
- Restored from backup. No help.
- This behavior appeared to be attributed to memory issues, so shut down every single service on the box. No help.
Note that there was an outage at the Oracle Cloud data center, which killed our VM. All problems started happening after the VM was started up.
Solution
1. Memory hardware issue. Rebuild the VM.
For example:
a. Stop the VM.
b. Create a new VM.
c. Mount the storage volumes on the new VM.
d. Rename the hostname of the new VM.
e. Everything will start up smoothly with no problems.
Applicable Versions
- Oracle WebLogic Server (10.3.6)
- Oracle Cloud Infrastructure (2019)
