Error Writing History Database File
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 561 Star 9,038 Fork 1,270 influxdata/influxdb Code Issues 407 Pull requests 36 Projects 0 Wiki Pulse Graphs New issue CLI History Error on ARM #6070
Error Writing To Database Moodle
Open rossmcdonald opened this Issue Mar 21, 2016 · 17 comments Projects None yet error writing to program database Labels None yet Milestone No milestone Assignees No one assigned 15 participants rossmcdonald commented Mar 21, 2016 When error writing to program database check for insufficient disk space running the InfluxDB CLI on ARM Linux (specifically Raspbian), the command history returns the error: There was an error writing history file: open : no such file or directory Even though the user is set
Fatal Error Lnk1201 Error Writing To Program Database
appropriately. Based on this comment, it seems like the file history path isn't being set correctly. rossmcdonald referenced this issue Mar 21, 2016 Closed [repo] add support for raspbian #5112 drdran commented Apr 3, 2016 Hi I have the same problem. jonseymour commented Apr 4, 2016 FWIW: i can reproduce the same symptom on linux/amd64 if I compile the influx binary with CGO_ENABLED=0 set in the environment. In this case, the
Influxdb
reason is that user.Current() then fails with the error: 'Current not implemented on linux/amd64.' This causes the branch in this block to be skipped, which then results in the reported symptom after a command is run (since the history path is never initialised properly). So, I suspect the reason this is occurring on ARM systems is either that the ARM build of the influx binary was done with CGO_ENABLED=0 for some reason or go has not implemented user.Current() for ARM systems for some different reason. jonseymour commented Apr 4, 2016 Based on a quick review of the go source, it seems more likely that the ARM influx binary was compiled with CGO_ENABLED=0 or, alternatively, that the user.Current() call is failing for some other reason on ARM systems. xmoulin commented Apr 10, 2016 same problem: uname -a Linux Nas-XMN 3.2.40 #7321 SMP Wed Mar 23 11:47:17 CST 2016 armv7l GNU/Linux synology_armada375_ds215j influx -version InfluxDB shell 0.12.1 jorgebonilla commented Apr 10, 2016 Same issue on a beaglebone (arm based). root@beaglebone:~# uname -a Linux beaglebone 4.1.15-ti-rt-r43 #1 SMP PREEMPT RT Thu Jan 21 20:13:58 UTC 2016 armv7l GNU/Linux root@beaglebone:~# influx --version InfluxDB shell 0.12.0 root@beaglebone:~# influx Visit https://enterprise.influxdata.com to register for updates, InfluxDB server management, and monitoring. Connected to http://localhost:8086 version 0.12.0 Inf
Sign in Pricing Blog Support Search GitHub This repository Watch 561 Star 9,038 Fork 1,270 influxdata/influxdb Code Issues 407 Pull requests 36 Projects grafana 0 Wiki Pulse Graphs New issue [repo] add support for raspbian #5112 Closed srsabu opened this Issue Dec 14, 2015 · 10 comments Projects None yet Labels area/packaging kind/feature request Milestone No milestone Assignees rossmcdonald 6 participants srsabu commented Dec 14, 2015 It would be great to have packages for raspbian on the Raspberry Pi. It https://github.com/influxdata/influxdb/issues/6070 isn't difficult to compile but just adds another set of steps to get a new station up and running and then similar additional steps when upgrading. rossmcdonald self-assigned this Dec 14, 2015 rossmcdonald added the category/packages label Dec 14, 2015 rossmcdonald commented Dec 14, 2015 @srsabu Thanks! We are planning on adding ARM builds to the repo shortly. I'll update https://github.com/influxdata/influxdb/issues/5112 this issue once it's done. beckettsean added the category/feature request label Jan 5, 2016 bwolf referenced this issue Jan 10, 2016 Merged Packaging arch argument for build.py. #5330 1 of 4 tasks complete nsteinmetz commented Feb 6, 2016 Also interested as I have some build issues with 0.10.0 as described in #5560 More than raspbian only, it would be more deb packages for armv6 and armv7 repositories. s1m0 commented Feb 24, 2016 Following #5330 the .deb packages are being built (since 0.10.0 beta2) but the package architecture is still "arm", not "armhf" so they won't install. $ sudo dpkg -i influxdb_0.10.1-1_arm.deb dpkg: error processing influxdb_0.10.1-1_arm.deb (--install): package architecture (arm) does not match system (armhf) Errors were encountered while processing: influxdb_0.10.1-1_arm.deb rossmcdonald commented Feb 24, 2016 @s1m0 The next release should have the corrected architecture. In the meantime you should be able to install the arm architecture by using the following command: dpkg --add-architecture arm dpkg -i
It is currently 3:20am, Sat 15 Oct, 2016 Database error 3 - Error writing file '/tmp/ (Errcode: 28) Advanced Questions & Problems Post a reply 14 posts • Page 1 of 1 Database error 3 - Error writing file https://forums.phplist.com/viewtopic.php?t=17708 '/tmp/ (Errcode: 28) by Heritage » 9:28pm, Wed 30 Apr, 2008 When going to: /lists/admin/?page=list The page now just shows a blank page or a time out from the server specific error. When digging further by manually going to: /lists/admin/?page=members&id=14 (or any ID for that manner) We get a error highlighted in red of: Database error 3 while doing query Error writing file '/tmp/MY7z6ruB' ( Errcode: 28 ) We see this specific error error writing is suppose to be due to drive space allocation; however, we are only using 1% of our tmp folder. Temp folders on Linux are set to 471M. So my question(s) are: Could PHPlist need more than 445 megs from the tmp when running queries? Would deleting user_history and usermessage help the issue? (Our host might do some mods to increase the tmp allocation, but by default we do not want to create more error writing to issues without some research.) Any info would be helpful. Thanks. Heritage Moderator Posts: 223Joined: 3:25pm, Fri 23 Jun, 2006Location: 800 720-7301 YIM Top Update: MySQL Error 28 by Heritage » 12:41pm, Thu 01 May, 2008 Update from my Host: There is enough space available under /tmp. Please note the tmp_table_size currently is set to 5MB which means it can consume 5MB space from the memory to complete its query. In case it needs more space than 5MB, mysql creates a disk-based table in /tmp directory to run its query. . . . So I have requested with my host that the MySQL tmp_table_size to be increased to 100 MB (if the table is a dedicated table allocating on the drive by size or 400 MB if the temp_table_size is a dynamic allocation of space). I hope this is going in the right direction. It seems I am getting outsourced "tech support" from my host. I would log into the database, but the site I am working on is on a dedicated box with other sites of mine. So each phpMyAdmin is stripped of it's full features for each of the site logins. If this does not work I am going to ask for a root login to the main phpMyAdmin and configure the MySQL default setti