Project

General

Profile

Bug #24095

collectd error "No such file or directory" after replication

Added by Stephen Makk over 3 years ago. Updated almost 3 years ago.

Status:
Closed: Not Applicable
Priority:
Important
Assignee:
Bartosz Prokop
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

This seems to be a common issue and frequently appears in forums without viable solutions. Have seen this with 9.10 and hoped upgrade to 11.0 would fix. Have two FreeNAS systems, one replicating to the other. Replication works properly and all sharing is functional on push and pull machines. Just get these constant errors....

collectd: 7537]: statvfs(/mnt/BakData/NasBak/Data) failed: No such file or directory


Related issues

Is duplicate of FreeNAS - Bug #24096: collectd error after replicationClosed: Duplicate2017-05-22

History

#1 Updated by Stephen Makk over 3 years ago

  • File debug-bnas-20170522112615.txz added

#2 Updated by William Grzybowski over 3 years ago

  • Assignee changed from William Grzybowski to Anonymous
  • Target version set to 11.1

#3 Updated by William Grzybowski over 3 years ago

  • Is duplicate of Bug #24096: collectd error after replication added

#4 Updated by Bartosz Prokop over 3 years ago

  • Assignee changed from Anonymous to Bartosz Prokop

#5 Updated by Bartosz Prokop over 3 years ago

  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Important

#6 Updated by Bartosz Prokop over 3 years ago

Stephen,

I've think you uploaded a wrong debug file. It is a HTML file not FreeNAS debug dump.

Can you upload correct one ?

Thanks

#7 Updated by Stephen Makk over 3 years ago

  • File debug-baknas-20170615203228.tgz added
  • Subject changed from collectd error "Na such file or directory" after replication to collectd error "No such file or directory" after replication

Problem persists after upgrade to 11 RELEASE
New debug file for replication destination server is attached.

#8 Updated by Stephen Makk over 3 years ago

  • File debug-nas-20170615203929.tgz added

Debug dump from replication source server also attached here.

#9 Updated by Bartosz Prokop over 3 years ago

Stephen,

Both debug dumps are once again an HTML file.

You can create valid debug dumps using GUI:

System -> Advanced -> Save Debug

Thanks,

Bartosz

#10 Updated by Stephen Makk over 3 years ago

That is how I made the dumps. Maybe Google Chrome is doing something wrong. I will re-do using FireFox.

#11 Updated by Stephen Makk over 3 years ago

  • File debug-baknas-20170619205124.tgz added

Debug from replication target, created using System -> Advanced -> Save Debug on Firefox, and uploaded using Firefox.

#12 Updated by Stephen Makk over 3 years ago

  • File debug-nas-20170619205643.tgz added

From replication source server

#13 Updated by Bartosz Prokop over 3 years ago

This is very strange... Those files are once again invalid.

We also need to solve this additional problem.

The other way of providing debug information is creating a debug file from shell.

This is the official documentation:

http://doc.freenas.org/9.10/cli.html?highlight=freenas%20debug#freenas-debug

After running the freenas-debug -A, please make an tar archive of /var/tmp/fndebug directory and attach it here.

Thanks in advance,

Bartosz

#14 Updated by Stephen Makk about 3 years ago

  • File baknas.tar added
  • File nas.tar added

Here are the tar files of debug info extracted via shell.
I had to reinstall the OS on one unit Something corrupted the boot drive in the midst of all this.

#15 Updated by Stephen Makk about 3 years ago

Problem persists after upgrade to FreeNAS-11.0-U1 (aa82cc58d)
It also appears that the continual logging activity burns out USB flash drives at a rate of about one per month.
Running mirrored 32 GB USB sticks for boot.

#16 Updated by Stephen Makk about 3 years ago

  • File baknas.tar added
  • File nas.tar added

Here are debug files from latest version.
Nas is also having problems. Collectd keeps reporting inability to sense CPUs or something.
Now both my servers are constantly filling their logs with apparently harmless errors.

#17 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Seen in changed from Unspecified to N/A

#18 Updated by Stephen Makk almost 3 years ago

Issue continues after upgrade to 11.0-U4

#19 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 3 years ago

  • Target version changed from 11.1 to 11.1-U1

#20 Updated by Dru Lavigne almost 3 years ago

  • Status changed from Screened to 15
  • Seen in changed from N/A to 11.0-RC2

Stephen: is this still an issue after updating to 11.1? If so, please attach a debug from the updated system.

#21 Updated by Stephen Makk almost 3 years ago

Problem no longer exists after upgrade to 11.1 I consider the issue closed.

#22 Updated by Dru Lavigne almost 3 years ago

  • Status changed from 15 to Closed: Not Applicable
  • Target version changed from 11.1-U1 to N/A
  • Private changed from Yes to No

Thanks for the update Stephen!

#23 Updated by Dru Lavigne almost 3 years ago

  • File deleted (debug-bnas-20170522112615.txz)

#24 Updated by Dru Lavigne almost 3 years ago

  • File deleted (debug-baknas-20170615203228.tgz)

#25 Updated by Dru Lavigne almost 3 years ago

  • File deleted (debug-nas-20170615203929.tgz)

#26 Updated by Dru Lavigne almost 3 years ago

  • File deleted (debug-baknas-20170619205124.tgz)

#27 Updated by Dru Lavigne almost 3 years ago

  • File deleted (debug-nas-20170619205643.tgz)

#28 Updated by Dru Lavigne almost 3 years ago

  • File deleted (baknas.tar)

#29 Updated by Dru Lavigne almost 3 years ago

  • File deleted (nas.tar)

#30 Updated by Dru Lavigne almost 3 years ago

  • File deleted (nas.tar)

#31 Updated by Dru Lavigne almost 3 years ago

  • File deleted (baknas.tar)

Also available in: Atom PDF