raft/shard log errors #311

Closed
Dieterbe opened this Issue Mar 7, 2014 · 5 comments

Comments

Projects
None yet
4 participants
@Dieterbe
Contributor

Dieterbe commented Mar 7, 2014

while testing out #293 I noticed this in the daemon output:
https://gist.github.com/Dieterbe/9413295
right now:

~ ❯❯❯ ls -alh /tmp/influxdb/development/db/shard_db/00001/                                                                                    ⏎
total 28M
drwxr-xr-x 2 dieter dieter  180 Mar  7 11:14 .
drwxr--r-- 5 dieter dieter  100 Mar  7 10:22 ..
-rw-r--r-- 1 dieter dieter  26M Mar  7 10:23 000005.sst
-rw-r--r-- 1 dieter dieter 2.0M Mar  7 11:28 000006.log
-rw-r--r-- 1 dieter dieter 745K Mar  7 11:14 000007.sst
-rw-r--r-- 1 dieter dieter   16 Mar  7 10:22 CURRENT
-rw-r--r-- 1 dieter dieter    0 Mar  7 10:22 LOCK
-rw-r--r-- 1 dieter dieter  453 Mar  7 11:14 LOG
-rw-r--r-- 1 dieter dieter  64K Mar  7 10:22 MANIFEST-000002
~ ❯❯❯ 

although i did restart influx a few times in the meantime.

@pauldix pauldix added this to the 0.5.0 milestone Mar 7, 2014

@jvshahid

This comment has been minimized.

Show comment Hide comment
@jvshahid

jvshahid Mar 7, 2014

Contributor

I think your tmp directory was nuked somehow. Did you do anything that could delete your tmp directory or is this something that you can easily reproduce ?

Contributor

jvshahid commented Mar 7, 2014

I think your tmp directory was nuked somehow. Did you do anything that could delete your tmp directory or is this something that you can easily reproduce ?

@Dieterbe

This comment has been minimized.

Show comment Hide comment
@Dieterbe

Dieterbe Mar 7, 2014

Contributor

i don't think i did anything to my /tmp
haven't seen it happen again, but if it happens again, anything specific i should look at?

Contributor

Dieterbe commented Mar 7, 2014

i don't think i did anything to my /tmp
haven't seen it happen again, but if it happens again, anything specific i should look at?

@jvshahid

This comment has been minimized.

Show comment Hide comment
@jvshahid

jvshahid Mar 7, 2014

Contributor

no just ls tmp and make sure that the entire directory isn't gone. You can also check your cron to make sure you don't have a script that constantly clean up tmp.

I'll go ahead and close this issue, please reopen if you successfully repro this issue.

Contributor

jvshahid commented Mar 7, 2014

no just ls tmp and make sure that the entire directory isn't gone. You can also check your cron to make sure you don't have a script that constantly clean up tmp.

I'll go ahead and close this issue, please reopen if you successfully repro this issue.

@jvshahid jvshahid closed this Mar 7, 2014

@Dieterbe

This comment has been minimized.

Show comment Hide comment
@Dieterbe

Dieterbe Mar 7, 2014

Contributor

note that most (if not all) common linux distributions implement the FHS (file hierarchy standard) which specifies that /tmp can be cleaned at any time.

quote man hier:

       /tmp   This directory contains temporary files which may be deleted with no notice, such as by a regular job or at system boot up.
Contributor

Dieterbe commented Mar 7, 2014

note that most (if not all) common linux distributions implement the FHS (file hierarchy standard) which specifies that /tmp can be cleaned at any time.

quote man hier:

       /tmp   This directory contains temporary files which may be deleted with no notice, such as by a regular job or at system boot up.
@elcct

This comment has been minimized.

Show comment Hide comment
@elcct

elcct Mar 7, 2014

Contributor

A lot of distributions use tmpfs filesystem for /tmp point, which means all data will be gone after reboot

Contributor

elcct commented Mar 7, 2014

A lot of distributions use tmpfs filesystem for /tmp point, which means all data will be gone after reboot

mnuessler pushed a commit to mnuessler/influxdb that referenced this issue May 22, 2015

Merge pull request #311 from vmarmol/fix
Fix Docker ALL reference
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment