UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
1335 views

AFP not loading

Hello, I have a server that AFP was working OK until today. The server is SLESsp1 and OES11. LUM is working, NSS is working. These stuff is from the afp log:

Apr 4 19:52:43 blackhawk afptcpd[17618]: Configuration file has DHX2 method set as UAM
Apr 4 19:52:43 blackhawk afptcpd[17618]: Configuration file has maximum number of threads set to 32
Apr 4 19:52:43 blackhawk afptcpd[17618]: Configuration file has max reconnect period set to 1440 minutes
Apr 4 19:52:43 blackhawk afptcpd[17618]: Configuration file has support for ALL AFP versions (2.2, 3.0, 3.1) set
Apr 4 19:52:43 blackhawk afptcpd[17618]: Configuration file has sharing-from-mac set to 'default'
Apr 4 19:52:43 blackhawk afptcpd[17618]: Configuration file has debug log set
Apr 4 19:52:43 blackhawk afptcpd[17618]: Configuration file has AUDIT disabled
Apr 4 19:52:43 blackhawk afptcpd[17618]: Configuration file has export all volumes enabled
Apr 4 19:52:43 blackhawk afptcpd[17640]: [error] PID file does not exist [No such file or directory]
Apr 4 19:52:43 blackhawk afptcpd[17640]: PID [17640] file created successfully
Apr 4 19:52:43 blackhawk afptcpd[17640]: Core dump limit - unlimited
Apr 4 19:52:43 blackhawk afptcpd[17640]: MALLOC_CHECK_ value - 2
Apr 4 19:52:43 blackhawk afptcpd[17640]: Maximum open files - 50000


I tried OES reconfiguration, reinstalled AFP.

Thanks in Advanced
Labels (2)
Tags (1)
0 Likes
3 Replies
Fleet Admiral
Fleet Admiral

hme0 wrote:

> Hello, I have a server that AFP was working OK until today. The server
> is SLESsp1 and OES11. LUM is working, NSS is working. These stuff is
> from the afp log:


...snip...

> APR 4 19:52:43 BLACKHAWK AFPTCPD[17640]:- [ERROR] PID FILE DOES NOT
> EXIST [NO SUCH FILE OR DIRECTORY]-
> APR 4 19:52:43 BLACKHAWK AFPTCPD[17640]: PID [17640] FILE CREATED
> SUCCESSFULLY


These are the only possibly interesting log entries from those you posted
but it's saying it created the PID file successfully so I think a red
herring.

> I tried OES reconfiguration, reinstalled AFP.


You say your server is "SLESsp1 and OES11" (you mean SLES11 SP1) but what
patch level?
What version of AFP? Please post output from "rpm -qa | grep afptcpd"
Have any changes been made recently to the server? Patches,
reconfiguration, additional packages (RPMs), etc.

HTH.
--
Simon
Novell Knowledge Partner
0 Likes
Absent Member.
Absent Member.

Thank you for your reply!

Sorry I meant SLES 11 SP1 and OES 11
blackhawk:~ # rpm -qa | grep afptcpd
novell-afptcpd-1.3.0-34.19

I ran the Online Updates most of them were security patches. Tomcat was updated. AFP was running fine after the update, I re-ran LUM because I was having issues with iManager not displaying Linux enabled services, so right after this AFP stop working.
Would it have anything to do with the registry?
smflood;2256354 wrote:
hme0 wrote:

> Hello, I have a server that AFP was working OK until today. The server
> is SLESsp1 and OES11. LUM is working, NSS is working. These stuff is
> from the afp log:


...snip...

> APR 4 19:52:43 BLACKHAWK AFPTCPD[17640]:- [ERROR] PID FILE DOES NOT
> EXIST [NO SUCH FILE OR DIRECTORY]-
> APR 4 19:52:43 BLACKHAWK AFPTCPD[17640]: PID [17640] FILE CREATED
> SUCCESSFULLY


These are the only possibly interesting log entries from those you posted
but it's saying it created the PID file successfully so I think a red
herring.

> I tried OES reconfiguration, reinstalled AFP.


You say your server is "SLESsp1 and OES11" (you mean SLES11 SP1) but what
patch level?



What version of AFP? Please post output from "rpm -qa | grep afptcpd"


Have any changes been made recently to the server? Patches,
reconfiguration, additional packages (RPMs), etc.


HTH.
--
Simon
Novell Knowledge Partner
0 Likes
Absent Member.
Absent Member.

Hello, I fixed the issue. I found an article about it. Something to do with the registry!
here is what I did:

To verify the existence of registry content perform from step 7 to step 10
of
the below procedure. If the content in the respective directories as
mentioned in step 9 does not exist, perform the following steps to rebuild the xtier
registry:

1. Open the terminal console and stop the xregd user by entering the
following command:
rcnovell-xregd stop
2. Export the registry in xml file of /var/opt/novell/xtier/xregd/db
/opt/novell/xtier/bin/regutil -e oldReg
3. Navigate to /var/opt/novell/xtier/xregd/db/ and enter ls -l to verify
that the folder db is empty. If the folder is empty, continue with step 5.
4. If any files exist inside the db folder, move all the files to the
temporary folder, for example /tmp.
5. Generate files inside the xtier registry by using the following
command:
a. Restore default registry.
/opt/novell/xtier/bin/regutil -i /etc/opt/novell/xtier/xtier_registry.xml
6. Navigate to /var/opt/novell/xtier/xregd/db/ and ensure that the
following files are generated by ls –l /var/opt/novell/xtier/xregd/db:
xtier_registry.db
xtier_registry.lck
xtier_registry.rfl
7. Start the xregd user by entering the following command:
rcnovell-xregd start
8. Navigate to the xtier registry by using the following command:
/opt/novell/xtier/bin/regedit
9. At the regedit prompt, execute the cd local_machine command and
enter
the ls -l command to view the content inside the directory. If the folder
software is present in the local_machine directory, then the registry is
rebuilt without any error.
10. Similarly, enter the following commands in the listed sequence and
enter the ls -l command to view the content in the respective directories:
cd software
cd Novell
cd Xtier
cd Configuration

If the content exists in all the respective directories, then the xtier
registry is completely rebuilt.
11. Enter exit.
12. Restart the machine
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.