Based on your information:
- You are trying to do a
connect()
to54.x.x.x
- The socket is
non-blocking
- Connection timeout is
60 sec
First, if you look into your /usr/include/asm-generic/errno.h
you’ll see the following:
#define EINPROGRESS 115 /* Operation now in progress */
It means an existing operation on the socket is in progress. Since, you said you are doing a connect()
call, lets do a man connect
:
EINPROGRESS The socket is nonblocking and the connection cannot be completed immediately. It is possible to select(2) or poll(2) for completion by selecting the socket for writing. After select(2) indicates writability, use getsockopt(2) to read the SO_ERROR option at level SOL_SOCKET to determine whether connect() completed successfully (SO_ERROR is zero) or unsuccessfully (SO_ERROR is one of the usual error codes listed here, explaining the reason for the failure).
So, the best guess would be that the TCP 3-way handshake (your connect()
call to 54.x.x.x
IP address) is taking longer than expected to complete. Since the connect()
operation is already in progress, any subsequent operation on the socket is resulting into EINPROGRESS
error code. As suggested in the man page, try to use select()
or poll()
to check if your socket is ready to use (to perform read()
or write()
calls).
You can pin-point what is preventing your TCP handshake to complete by capturing and analyzing the traffic to/from your own machine and 54.x.x.x
. The best tool to help you with this is called WireShark. Good luck.
- Печать
Страницы: [1] Вниз
Тема: Transmission. Operation now in progress. (Прочитано 1467 раз)
0 Пользователей и 1 Гость просматривают эту тему.
Atilla
Решил скачать netbook remix 9.04 (947 метров).
Скачивает пару минут и автоматически встает на паузу. В ошибку выдает Operation now in progress.
Вроде тоже сталкивался кто-то с такой проблемой:
http://forum.transmissionbt.com/viewtopic.php?f=2&t=5677
Но там на буржуйском. Вроде как проблема была в файловой системой или размером файла.
А у меня с такой же ФС катает на другом компе. Без проблем. Тоже 9.04 & Transmission.
Одним словом что может быть?
Nick F0x
там написано, что проблема решена, и было дело-то с очень старой версией, в вики пишут, что проблема или с фс (объёмом свободного места или ошибками в самой фс), или винт сыпется, нужно решать.
топистартер не указал версию transmission, гадать сложно)
Atilla
Компу недели нет. И вряд ли в фс ошибка. Значит обновлять…
Nick F0x
Компу недели нет. И вряд ли в фс ошибка.
согласиться с подобным утверждением не могу
Atilla
>> согласиться с подобным утверждением не могу.
хмммм. Я прям призадумался. А как это можно проверить?
AnrDaemon
Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.
Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…
- Печать
Страницы: [1] Вверх
- Печать
Страницы: [1] Вниз
Тема: Transmission. Operation now in progress. (Прочитано 1359 раз)
0 Пользователей и 1 Гость просматривают эту тему.
Atilla
Решил скачать netbook remix 9.04 (947 метров).
Скачивает пару минут и автоматически встает на паузу. В ошибку выдает Operation now in progress.
Вроде тоже сталкивался кто-то с такой проблемой:
http://forum.transmissionbt.com/viewtopic.php?f=2&t=5677
Но там на буржуйском. Вроде как проблема была в файловой системой или размером файла.
А у меня с такой же ФС катает на другом компе. Без проблем. Тоже 9.04 & Transmission.
Одним словом что может быть?
Nick F0x
там написано, что проблема решена, и было дело-то с очень старой версией, в вики пишут, что проблема или с фс (объёмом свободного места или ошибками в самой фс), или винт сыпется, нужно решать.
топистартер не указал версию transmission, гадать сложно)
Atilla
Компу недели нет. И вряд ли в фс ошибка. Значит обновлять…
Nick F0x
Компу недели нет. И вряд ли в фс ошибка.
согласиться с подобным утверждением не могу
Atilla
>> согласиться с подобным утверждением не могу.
хмммм. Я прям призадумался. А как это можно проверить?
AnrDaemon
Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.
Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…
- Печать
Страницы: [1] Вверх
Номер ошибки: | Ошибка 0x800CCC45 | |
Название ошибки: | Operation now in progress | |
Описание ошибки: | Operation now in progress. This error appears if a Windows Sockets API is called while a blocking function is in progress. SMTP_NO_RECIPIENTS. | |
Разработчик: | Microsoft Corporation | |
Программное обеспечение: | Microsoft Outlook Express | |
Относится к: | Windows XP, Vista, 7, 8, 10, 11 |
«Operation now in progress» обычно является ошибкой (ошибкой), обнаруженных во время выполнения. Когда дело доходит до программного обеспечения, как Microsoft Outlook Express, инженеры могут использовать различные инструменты, чтобы попытаться сорвать эти ошибки как можно скорее. Тем не менее, возможно, что иногда ошибки, такие как ошибка 0x800CCC45, не устранены, даже на этом этапе.
Некоторые люди могут столкнуться с сообщением «Operation now in progress. This error appears if a Windows Sockets API is called while a blocking function is in progress. SMTP_NO_RECIPIENTS.» во время работы программного обеспечения. Если возникает ошибка 0x800CCC45, разработчикам будет сообщено об этой проблеме через уведомления об ошибках, которые встроены в Microsoft Outlook Express. Затем Microsoft Corporation будет иметь знания, чтобы исследовать, как и где устранить проблему. Чтобы исправить любые документированные ошибки (например, ошибку 0x800CCC45) в системе, разработчик может использовать комплект обновления Microsoft Outlook Express.
Что вызывает ошибку времени выполнения 0x800CCC45?
Сбой во время выполнения Microsoft Outlook Express, как правило, когда вы столкнетесь с «Operation now in progress» в качестве ошибки во время выполнения. Вот три наиболее распространенные причины, по которым происходят ошибки во время выполнения ошибки 0x800CCC45:
Ошибка 0x800CCC45 Crash — это типичная ошибка «Operation now in progress», которая приводит к полному завершению работы программы. Это происходит много, когда продукт (Microsoft Outlook Express) или компьютер не может обрабатывать уникальные входные данные.
Утечка памяти «Operation now in progress» — при утечке памяти Microsoft Outlook Express это может привести к медленной работе устройства из-за нехватки системных ресурсов. Это может быть вызвано неправильной конфигурацией программного обеспечения Microsoft Corporation или когда одна команда запускает цикл, который не может быть завершен.
Ошибка 0x800CCC45 Logic Error — Логическая ошибка возникает, когда ПК производит неправильный вывод, даже когда пользователь вводит правильный вход. Это может произойти, когда исходный код Microsoft Corporation имеет уязвимость в отношении передачи данных.
Как правило, такие Microsoft Corporation ошибки возникают из-за повреждённых или отсутствующих файлов Operation now in progress, а иногда — в результате заражения вредоносным ПО в настоящем или прошлом, что оказало влияние на Microsoft Outlook Express. Основной способ решить эти проблемы вручную — заменить файл Microsoft Corporation новой копией. Помимо прочего, в качестве общей меры по профилактике и очистке мы рекомендуем использовать очиститель реестра для очистки любых недопустимых записей файлов, расширений файлов Microsoft Corporation или разделов реестра, что позволит предотвратить появление связанных с ними сообщений об ошибках.
Распространенные сообщения об ошибках в Operation now in progress
Усложнения Microsoft Outlook Express с Operation now in progress состоят из:
- «Ошибка программного обеспечения Operation now in progress. «
- «Operation now in progress не является приложением Win32.»
- «Извините, Operation now in progress столкнулся с проблемой. «
- «Файл Operation now in progress не найден.»
- «Отсутствует файл Operation now in progress.»
- «Ошибка запуска программы: Operation now in progress.»
- «Файл Operation now in progress не запущен.»
- «Отказ Operation now in progress.»
- «Operation now in progress: путь приложения является ошибкой. «
Проблемы Operation now in progress с участием Microsoft Outlook Expresss возникают во время установки, при запуске или завершении работы программного обеспечения, связанного с Operation now in progress, или во время процесса установки Windows. Запись ошибок Operation now in progress внутри Microsoft Outlook Express имеет решающее значение для обнаружения неисправностей электронной Windows и ретрансляции обратно в Microsoft Corporation для параметров ремонта.
Причины проблем Operation now in progress
Проблемы Operation now in progress вызваны поврежденным или отсутствующим Operation now in progress, недопустимыми ключами реестра, связанными с Microsoft Outlook Express, или вредоносным ПО.
В основном, осложнения Operation now in progress связаны с:
- Поврежденная или недопустимая запись реестра Operation now in progress.
- Зазаражение вредоносными программами повредил файл Operation now in progress.
- Operation now in progress ошибочно удален или злонамеренно программным обеспечением, не связанным с приложением Microsoft Outlook Express.
- Другое приложение, конфликтующее с Operation now in progress или другими общими ссылками.
- Microsoft Outlook Express (Operation now in progress) поврежден во время загрузки или установки.
Продукт Solvusoft
Загрузка
WinThruster 2022 — Проверьте свой компьютер на наличие ошибок.
Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление
Based on your information:
- You are trying to do a
connect()
to54.x.x.x
- The socket is
non-blocking
- Connection timeout is
60 sec
First, if you look into your /usr/include/asm-generic/errno.h
you’ll see the following:
#define EINPROGRESS 115 /* Operation now in progress */
It means an existing operation on the socket is in progress. Since, you said you are doing a connect()
call, lets do a man connect
:
EINPROGRESS The socket is nonblocking and the connection cannot be completed immediately. It is possible to select(2) or poll(2) for completion by selecting the socket for writing. After select(2) indicates writability, use getsockopt(2) to read the SO_ERROR option at level SOL_SOCKET to determine whether connect() completed successfully (SO_ERROR is zero) or unsuccessfully (SO_ERROR is one of the usual error codes listed here, explaining the reason for the failure).
So, the best guess would be that the TCP 3-way handshake (your connect()
call to 54.x.x.x
IP address) is taking longer than expected to complete. Since the connect()
operation is already in progress, any subsequent operation on the socket is resulting into EINPROGRESS
error code. As suggested in the man page, try to use select()
or poll()
to check if your socket is ready to use (to perform read()
or write()
calls).
You can pin-point what is preventing your TCP handshake to complete by capturing and analyzing the traffic to/from your own machine and 54.x.x.x
. The best tool to help you with this is called WireShark. Good luck.
Не могу разобраться, почему вылетает ошибка: System.InvalidOperationException: An operation is already in progress.
Кусок кода который который если выкинуть, все работает нормально я пометил.
List<UserData> uds = new List<UserData>();
UserData ud;
List<string> dblist = GetListDBsList();
if (dblist.Contains(config.PGdbName))
{
Console.WriteLine("Data Base exists: {0}", config.PGdbName);
}
else
{
Console.WriteLine("Data Base DO NOT exists: {0}", config.PGdbName);
return;
}
NpgsqlConnection conn = new NpgsqlConnection("Server=127.0.0.1;Port=5432;User Id=" + config.PGLogin + ";" +
"Password=" + config.PGPass + ";Database=" + config.PGdbName + ";");
//select datname from pg_database;
try
{
conn.Open();
Console.WriteLine("PG Connected");
}
catch(SocketException e)
{
Console.WriteLine(e.Message);
}
//NpgsqlTransaction tr = conn.BeginTransaction();
// Где-то в этом блоке ошибка
string tablesListRequestSQL = @"SELECT table_name FROM information_schema.tables WHERE table_schema='public'";
NpgsqlCommand commandGetDBTables = new NpgsqlCommand(tablesListRequestSQL, conn);
NpgsqlDataReader drGetDBTables = commandGetDBTables.ExecuteReader();
//tr.Commit();
while (drGetDBTables.Read())
{
existsInDBTables.Add(drGetDBTables[0].ToString());
}
foreach (string table in requireTablesList) //
{
if (!existsInDBTables.Contains(table)) // if element from requireTablesList do not found -> DB have not simmilar Tables!
{
notFoundedTables.Add(table);
}
}
if (notFoundedTables.Count != 0) // if not empty
{
Console.WriteLine("Next tables are marked as reqired for Sync, but can't be found in DataBase: ");
foreach (var table in notFoundedTables)
{
Console.WriteLine(table);
}
}
// Конец блока где ошибка.
Console.ReadKey();
NpgsqlCommand command = new NpgsqlCommand("SELECT city, state FROM cities", conn);
try
{
NpgsqlDataReader dr = command.ExecuteReader();
while (dr.Read())
{
// UserData ud = new UserData();
ud.id = Int32.Parse(dr[0].ToString());
ud.guid = (dr[1].ToString());
ud.name = (dr[2].ToString());
ud.userblob = (byte[])dr[3];
uds.Add(ud);
//File.WriteAllBytes("outputimg.jpg", ud.userblob);
//Console.ReadKey();
}
}
finally
{
conn.Close();
}
Что не так делаю?
У нас есть gitlab pipeline, который раскатывает релизы в Kubernetes кластер. Подключение к GitLab не всегда оптимально, поэтому может случиться так, что развертывание не удастся из-за тайм-аута / проблем с сетью. Когда такое происходит то следующий запуск pipeline завершается неудачно, потому что helm сообщает об
ошибке:
Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress
helm history tax-service
REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION 1 Mon Apr 19 10:31:54 2021 superseded helm-1.0.0 1.0.0-ddc8267b Upgrade complete 2 Mon Apr 19 10:52:33 2021 superseded helm-1.0.0 1.0.0-522eebc2 Upgrade complete 3 Mon Apr 19 10:54:33 2021 pending-upgrade helm-1.0.0 1.0.0-39118b96 Preparing upgrade |
откатываемся:
helm rollback tax-service 1
REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION 4 Mon Apr 19 11:31:54 2021 superseded helm-1.0.0 1.0.0-ddc8267b Rollback to 1 5 Mon Apr 19 11:32:12 2021 deployed helm-1.0.0 1.0.0-fb2a5654 Upgrade complete |
проверяем:
helm history tax-service
REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION 1 Mon Apr 19 10:31:54 2021 superseded helm-1.0.0 1.0.0-ddc8267b Upgrade complete 2 Mon Apr 19 10:52:33 2021 superseded helm-1.0.0 1.0.0-522eebc2 Upgrade complete 3 Mon Apr 19 10:54:33 2021 pending-upgrade helm-1.0.0 1.0.0-39118b96 Preparing upgrade 4 Mon Apr 19 11:31:54 2021 superseded helm-1.0.0 1.0.0-ddc8267b Rollback to 1 5 Mon Apr 19 11:32:12 2021 deployed helm-1.0.0 1.0.0-fb2a5654 Upgrade complete |
после этого можно проверять и запускать pipeline
https://github.com/midnight47/
Based on your information:
- You are trying to do a
connect()
to54.x.x.x
- The socket is
non-blocking
- Connection timeout is
60 sec
First, if you look into your /usr/include/asm-generic/errno.h
you’ll see the following:
#define EINPROGRESS 115 /* Operation now in progress */
It means an existing operation on the socket is in progress. Since, you said you are doing a connect()
call, lets do a man connect
:
EINPROGRESS The socket is nonblocking and the connection cannot be completed immediately. It is possible to select(2) or poll(2) for completion by selecting the socket for writing. After select(2) indicates writability, use getsockopt(2) to read the SO_ERROR option at level SOL_SOCKET to determine whether connect() completed successfully (SO_ERROR is zero) or unsuccessfully (SO_ERROR is one of the usual error codes listed here, explaining the reason for the failure).
So, the best guess would be that the TCP 3-way handshake (your connect()
call to 54.x.x.x
IP address) is taking longer than expected to complete. Since the connect()
operation is already in progress, any subsequent operation on the socket is resulting into EINPROGRESS
error code. As suggested in the man page, try to use select()
or poll()
to check if your socket is ready to use (to perform read()
or write()
calls).
You can pin-point what is preventing your TCP handshake to complete by capturing and analyzing the traffic to/from your own machine and 54.x.x.x
. The best tool to help you with this is called WireShark. Good luck.
Here is the background scenario:
- You have a Windows based file share you want to access. This particular example uses WinXP Home as the server.
- You have a Linux based PC with Samba installed which is your client.
- You want to use cifs to attach the Windows based file share to your Linux based client.
The message: «mount error(115): Operation now in progress» indicates a failure to attach a Windows based file share using Samba. The following example is typical:
Code: |
# mount -t cifs //192.168.0.102/Software /mnt/sweet.softare
Password: mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) |
First, let’s make some things clear. If you’ve received this message, then the following is probably true:
- Samba is properly installed on your client PC.
- Your Samba configuration settings are probably correct.
- Your Windows host network settings are probably correct.
- The Windows based file share is visible and reachable from your client PC.
- You cannot connect to the shared printer you know is out there.
As far as I can tell, you only get this message if Samba ‘sees’ the share you want but cannot connect to it.
Edit: Point of clarification — In the examples below, you’ll notice I use a domain name of ‘lamasondufeu’. I always make use of a domain name on mixed networks in order to enforce Windows Workgroup naming consistency. By default, Samba will use the domain name of the computer it’s running on as the ‘Windows Workgroup’ unless you explicitly provide one in smb.conf. Also by default, WinXP always uses ‘workgroup’ as it’s value for ‘Windows Workgroup’.
All computers which expect to talk to each other using Windows {cifs based} networking need to either be in the same Workgroup or you need to explicitly which workgroups they are allowed to talk to. Selecting a specific domain name for your network and using that as your Windows Workgroup name makes mixed networks much easier to adminster. Also, it’s considered bad security practice to leave the Windows Workgroup name at it’s default value so this is something you want to change anyway.
It’s always good policy on multi-computer local networks to pick your own domain name and stick with it for that local network. End Edit
Before we run any diagnostics, we can see one immediate problem. Note the prompt for ‘Password:’.
First tip: WinXP Home has no support for password based file shares. Password based file shares are optional for WinXP Professional. In the Windows world, all simple file shares assume there are no username/password pairs. Therefore, the above command was incorrect.
When trying to attach any simple Windows based file shares, you need to add ‘-o guest’ to the mount command. Simple in this case means no password restricted file shares which means no user authentication of any kind. Repeat: All WinXP Home based file share are simple. Most home users of WinXP Professional will also be using simple file shares as will Win 7 users whose file shares are set in WinXP compatibility mode.
The above command should look more like this:
Code: |
# mount.cifs —verbose -o «guest,domain=lamasondufu» //192.168.0.100/Software /mnt/sweet.softare
mount.cifs kernel mount options: ip=192.168.0.100,unc=192.168.0.100Software,guest,ver=1,user=,domain=lamasondufu,pass=******** mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) |
This command also failed but we were no longer prompted for ‘Password’. Yeah! First problem resolved.
To head off a possible point of confusion, please note that mount -t cifs and mount.cifs are the exactly equivalent. All these examples are cut and pasted from real life.
The first diagnostic we need to run is smbtree. This will confirm everything that’s actually visible on the network from Samba’s point of view. The results should prove:
- You have Samba correctly installed.
- What file shares/printers are available for you to attach.
Do not run this diagnostic tool on a network with a lot of PCs. The options you should use are:
Code: |
-b, —broadcast Use broadcast instead of using the master browser
-N, —no-pass Don’t ask for a password |
These options will run smbtree without the need or confusion to determine who the ‘master browser’ is and restrict the output to simple shares (no password) only.
The following is a typical example from my home network:
Code: |
# smbtree -b -N
LAMASONDUFEU SWEET Mumzie MS SWEETSoftware SWEETCanonMX3 Canon MX360 series Printer SWEETSharedDocs SWEETprint$ Printer Drivers SWEETIPC$ Remote IPC SLIZARD Samba 3.6.5 SLIZARDHP_PhotoSmart_P1000 HP PhotoSmart P1000 SLIZARDPHOTOSMART-P1000 HEWLETT-PACKARD PHOTOSMART P1000 SLIZARDIPC$ IPC Service (Samba 3.6.5) SLIZARDprint$ Printer Drivers SLIZARDPUBROOT SLIZARDPUB04 SLIZARDPUB03 SLIZARDPUB02 SLIZARDPUB01 SLIZARDLIBRARY PYROTEKK Samba 3.6.5 PYROTEKKIPC$ IPC Service (Samba 3.6.5) PYROTEKKPUBROOT PYROTEKKPUBLIC PYRODYNO Samba 3.6.5 PYRODYNOIPC$ IPC Service (Samba 3.6.5) PYRODYNOPUBU06 PYRODYNOPUBU05 PYRODYNOPUBU04 PYRODYNOPUBU03 PYRODYNOPUBU02 PYRODYNOPUBU01 PYRODYNOPUBROOT PYRODYNOPUB02 PYRODYNOPUB01 PYRODYNOPUB00 |
If you’re on a network with more than a handful of computers, this listing can be quite long. Instead of running smbtree, you can run nmblookup. To run this command, you need an additional bit of information. That information is the IP address of the computer which hosts the file share you want to attach. As you can see from the above mount command, I have this information. There are one option you’ll want to use:
Code: |
-A, —lookup-by-ip Do a node status on <name> as an IP Address |
This option reduces all the actions needed to perform the query to the barest minimum possible. This is an important point with implications I’ll address further down.
Here is a typical example of the query:
Code: |
# nmblookup -A 192.168.1.100
Looking up status of 192.168.1.100 SWEET <00> — M <ACTIVE> LAMASONDUFEU <00> — <GROUP> M <ACTIVE> SWEET <20> — M <ACTIVE> LAMASONDUFEU <1e> — <GROUP> M <ACTIVE> MAC Address = 00-16-76-78-E4-4F |
The results show us two things:
- We have Samba properly installed.
- The file share host is visible on our network.
Now that we’ve verified Samba is working and that the host is visible, we’re ready to take the next diagnostic step. From both the smbtree and nmblookup commands, we know the Windows name of the host computer is SWEET. We therefore try our mount command using SWEET instead of 192.168.1.100:
Code: |
# mount.cifs —verbose -o «guest,domain=lamasondufu» //SWEET/Software /mnt/sweet.softare
mount error: could not resolve address for SWEET: Unknown error |
Second Tip: When one computer can’t find another computer by name, then we always punt. In this case, punting means to explicitly set up an entry in our local client’s /etc/hosts file for the target share server:
Code: |
# echo «192.168.1.100 SWEET sweet sweet.lamasondufeu» >> /etc/hosts |
We do this so that we rely upon only our local client and the target share host to establish a connection. It’s part of the bog standard diagnostic process to reduce number of possible failed components to the minimum needed.
Now, we try our mount command again:
Code: |
# mount.cifs —verbose -o guest //SWEET/Software /mnt/sweet.softare
mount.cifs kernel mount options: ip=192.168.1.100,unc=SWEETSoftware,guest,ver=1,user=,pass=******** # df -h Filesystem Size Used Avail Use% Mounted on rootfs 369G 299G 52G 86% / /dev/root 369G 299G 52G 86% / devtmpfs 3.7G 0 3.7G 0% /dev tmpfs 3.7G 436K 3.7G 1% /run shm 3.7G 724K 3.7G 1% /dev/shm /dev/sda1 31M 6.5M 23M 23% /boot /dev/sdb1 931G 910G 21G 98% /home /dev/sda4 559G 553G 4.2G 100% /pub00 /dev/sdc1 1.9T 1.8T 39G 98% /pub01 /dev/sdd1 1.9T 1.8T 34G 99% /pub02 /dev/loop0 9.4G 9.4G 0 100% /mnt/newsf /dev/sde1 931G 899G 32G 97% /pubu01 /dev/sdf1 1.9T 1.8T 20G 99% /pubu02 /dev/sdi1 1.4T 1.4T 21G 99% /pubu03 /dev/sdj1 1.9T 1.8T 20G 99% /pubu04 /dev/sdg1 1.9T 1.8T 40G 98% /pubu05 /dev/sdh1 1.4T 1.4T 16G 99% /pubu06 192.168.1.199:/home 234G 231G 2.9G 99% /mnt/slizard/home 192.168.1.199:/library 234G 85G 149G 37% /mnt/slizard/library 192.168.1.199:/pub01 931G 913G 17G 99% /mnt/slizard/pub01 192.168.1.199:/pub02 931G 896G 36G 97% /mnt/slizard/pub02 192.168.1.199:/pub03 931G 894G 38G 96% /mnt/slizard/pub03 192.168.1.199:/pub04 931G 909G 23G 98% /mnt/slizard/pub04 192.168.1.199:/pubroot 230G 177G 42G 81% /mnt/slizard/pubroot 192.168.1.197:/home 179G 101G 69G 60% /mnt/pyrotekk/home 192.168.1.197:/pub01 931G 860G 71G 93% /mnt/pyrotekk/pub01 192.168.1.197:/public 1.2T 1.1T 73G 94% /mnt/pyrotekk/public 192.168.1.197:/pubroot 179G 101G 69G 60% /mnt/pyrotekk/pubroot 192.168.1.197:/mnt/temp1 1.4T 1.4T 63G 96% /mnt/pyrotekk/temp1 192.168.1.197:/mnt/temp2 1.4T 1.4T 39G 98% /mnt/pyrotekk/temp2 //SWEET/Software 53G 18G 36G 34% /mnt/sweet.softare |
Success!! We can now access file shares and printer shares on the target host computer.
This is not the ideal solution. Rather the ‘name’ of the target share host and its associated IP address is supposed to be already available on our network. Moreover, this is supposed to happen automatically.
Observations:
- In this case SWEET (as can be seen from the nmblookup results) is the wins master browser on my local network. Yet no name/address association was available. I have had problems in the past with the wins master browser service in mixed environments. Crap happens. I should probably force configure the samba daemon on my internal network’s server (SLIZARD) to be wins master browser.
- In home networks which use an off the shelf router to connect to the internet, it is my personal observation that local name resolution may not happen. The default configuration of the OTS router is to support DNS service pass through for queries outside of the local lan.
- As far as I’ve experienced, all distributions perform minimalist configuration installations. This means that these minimal configuration settings may assume working services that are not actually working such as a working wins or dns service.
- Because of things like local caching (share name and IP being retained across reboots over time), it is possible for one client PC to have no problem with making a share connection while another either loses that ability or is never able to attach the share. Don’t make the mistake of saying one PC is broken because another PC is still works.
- In fact, said cached information can be lost due to simply performing an upgrade. It’s not that the updated programs are broken. Instead, all the cached values are cleared during the upgrade. If your wins master browser is not working properly, then your wins resolution will never happen.
- Depending on which machine on your network is the wins master browser and the version of Windows it’s running, the strategy employed to refresh the wins master browser cache can range from stupid to really, really stupid. It is my understanding that after a wins master browser first initializes it’s cache, it won’t walk the local network again looking for new additions. Rather, it expects new additions to the local network to essentially add themselves.
- Name resolution goes through a descending hierarchy of protocols. The last resort bottom name resolution protocol simply checks the /etc/hosts file. In theory however, explicitly specifying an IP address is supposed to always work too. I’m still surprised that my original mount command did not work. On the other hand, the added entry to the /etc/hosts file did work.
- In my research for my issue, I encountered another known class of problems which can cause a mount error(115): Operation now in progress message. This is when the same nic (on the target share host) might be using more than one IP address. There are numerous valid circumstances for this including setting up virtual networks and the ability to add USB drives to routers for direct availability of said drives over a local network. In essence, the wins resolver associates the desired name with the wrong IP address.
The bottom line is that if you see a mount error(115): Operation now in progress message when trying to mount any cifs based network share, you most likely have a name resolution problem. Your equipment, software and physical connections are probably all fine. I re-iterate: Don’t simply assume your equipment is broken or an upgrade was faulty or even that your configuration may be incorrect. Things may actually be working as designed.
In my example, lack of an internally available DNS combined with a stupid wins master browser are the root cause.
This episode has enhanced my motivation to build (re-purpose) a custom router again with a proper DNS as well as forcing it to be th wins master browser.
Further Readings
Threads which may be of interest in terms of the above discussion and hindsight perspective:
Samba Oddities
cifs-utils: Windows share cannot be mounted anymore after dist-upgrade
Mount Error
Error -115 when mounting share (cifs)
Mounting a Windows computer with two IP addresses
_________________
People whom think M$ is mediocre, don’t know the half of it.