mysql"Out of resources when opening file"错误怎么解决？

bdgoog 2013-06-06 09:23:41

多个网站在同一台服务器上，访问其中一个网站的时候，出现如下的错误提示：
MySQL server error report:Array ( [0] => Array ( [message] => MySQL Query Error ) [1] => Array ( [sql] => INSERT INTO `feokj_shop`.`ecs_sessions` (sesskey, expiry, ip, data) VALUES ('38796f5e5768b6d922cb7ece9ea9b02a', '1370523934', '123.116.229.194', 'a:0:{}') ) [2] => Array ( [error] => Out of resources when opening file '.\feokj_shop\ecs_sessions.MYD' (Errcode: 24) ) [3] => Array ( [errno] => 23 ) )
其它网站可以正常访问。请大家帮帮忙。多谢

...全文

305 4 打赏收藏转发到动态举报

写回复

4 条回复

切换为时间正序

请发表友善的回复…

发表回复

bdgoog 2013-07-12

打赏
举报

回复

是服务器负载太大了

rucypli 2013-06-11

打赏
举报

回复

引用 2 楼 bdgoog 的回复:

经常出现这种错误，Can't create/write to file '#sql_d28_0.MYD' (Errcode: 17) ) [3] => Array ( [errno] => 1 ，服务器没装麦克菲

看一下mysql设置的tmpdir路径是否太小

bdgoog 2013-06-10

打赏
举报

回复

经常出现这种错误，Can't create/write to file '#sql_d28_0.MYD' (Errcode: 17) ) [3] => Array ( [errno] => 1 ，服务器没装麦克菲

rucypli 2013-06-06

打赏
举报

回复

ulimit -a看看是否打开最大文件数设置的太小

Build Report Tool README Note: If you are upgrading Build Report Tool in your project, delete the current BuildReport folder first before importing the new one! This will eliminate any potential metadata file conflicts with the old Build Report Tool. To show the Build Report Window, go to Window > Show Build Report. If Build Report Tool doesn't show up when you do that, you may have to reset your Unity Editor layout. Choose Window > Layouts > Default. Then try opening the Build Report Window again. === Important Notes === In case you get any build errors that you think might be caused by the Build Report Tool, try disabling the Build Report Window from showing automatically whenever you build. You can do this by opening the Build Report window, going to options, then uncheck "Collect and save build info automatically after building". If that doesn't work, you can simply delete the files in the Build Report Tool as a last resort. === Erroneous Values === The Build Report Tool gets much of its data from the Unity Editor's log file. Extremely large projects with large file sizes may get erroneous values. If you experience this, check your Editor log file: Go to your Console View (go to Window > Console, or press ctrl + shift + C). In the Console View's upper right corner, click the button "Open Editor Log". If the Unity Editor's log file itself is showing wrong values for your file sizes, you may want to submit a bug report to Unity (go to Help > Report a Bug). === How to use === To show the Build Report Window, go to Window > Show Build Report. Make sure you build your project first. If not, Build Report Tool has no data to get and will not work. However, it won't care if the project you built last time isn't the same one you currently have open. So it's always best to build your project before you look at the Build Report Window. You can also save build reports to XML files, or open previously saved ones. Whenever you build your project, the Build Report Tool will automatically generate a build report and save it. If you don't want the Build Report Tool to do that automatically, you can disable it in the options. === Parts === A build report is broken into five main categories: 1. Overview: Summary of the report. 2. Project Settings: Shows project settings that were used upon time of building. 3. Size Stats: Shows the build's file size, and a table breaking down of which assets are taking up what percentage of space on the build. 4. Used Assets: Shows a list of *all* assets that were included in the build, along with how much space they take. 5. Unused Assets: Shows a list of assets in the project that were *not* used for the build. This is useful for finding out which assets are not used anymore that perhaps you may want to delete to save space. === What's counted in the Build Report === The Build Report only takes into account your assets' size, plus managed DLLs. The real final size of your build may be larger or smaller depending on the platform. In desktop and mobile builds, the build size reflects the size of the resulting sharedassets0.assets, sharedassets1.assets (and so on) files that are generated. Also counted are the files in the "Managed" folder (Mono DLLs, your scripts in compiled DLL form, plus other managed DLLs in your project). All other files are not counted in the total build size. That includes native plugins. But take note, native plugins will still show up in the asset lists, it is only that their size that is not counted in the "Total Used Assets Size". Files in your StreamingAssets folder are not included in the "Used Assets Size Breakdown" table. However, their total size is still indicated, and those files are still included in the "Used Assets" list. In desktop builds, you may find a "unity default resources" file in your build. Inside that are defaults, like the default GUI Skin, default font for the GUI, default shaders, the built-in cube, cylinder, or capsule, default white material, etc. That file is also not counted in the Build Report. See discussion here: http://forum.unity3d.com/threads/120081-unity-default-resources In Windows, your resulting .exe file is also not considered in the Build Report as that is considered a "boilerplate" resource. The contents of your .exe file is largely standard among all Windows programs built in Unity, with some minor changes. In web builds, your .unity3d file is a compressed archive of all your used assets, your Unity scene files, your scripts' resulting managed DLLs, any managed DLLs from the Mono standard library your build needs, plus any managed DLLs that you explicitly included. Take note there are several Mono libraries that cannot be included for web due to considerations for web browser security. In iOS builds, the total build size only represents the size of the game before it gets compiled and packaged into an .app file in Xcode. The size may get smaller once it gets packaged into an .ipa file. Note: Managed DLLs mean DLL files containing compiled .NET/Mono code. Native DLLs mean DLL files built out of code that wasn't .NET/Mono (usually C/C++). === Prefab Instances in Scenes === If you have prefab instances in a scene, they don't actually count in the editor log's build info. Why exactly, I'm not sure. My guess is things work this way: Actually during runtime, the concept of prefabs do not exist anymore. As far as Unity is concerned, they are all just game objects. Instantiate actually merely duplicates/clones an existing game object (whether it is currently residing in the scene or exists as a prefab in the assets folder). (side note: you can actually use Instantiate to duplicate a game object, even if it is not a prefab) As such, during runtime, prefab connections get lost. Once you run the game, prefab instances are simply considered regular game objects. I assume the same thing happens when you build your game. So the prefab files in your project are not included in the build. Instead, the individual prefab instances that are in your scenes are the ones counted in the file size (technically their file sizes are in the scene files' file sizes). Two exceptions: 1. If your prefab file is in a Resources folder, it gets included in the build. 2. If your prefab is referenced from a script via a variable/field, then it is included in the build. Basically what it means is if you created your code in such a way that you need to instantiate a prefab at runtime (regardless of whether an instance of it is in the scene already or not) then Unity has no choice but to include it in the build. So you may find some prefab files in the "Used Assets" section that do not show a size reading. Those are the prefabs that were used in scenes but are not in a Resources folder, nor referenced as a variable. === Size Readings === Why is the build size larger when shown in Windows Explorer? You may find that the sizes in the Build Report Tool are different from the sizes of the files on disk. This is normal. Here is a good explanation why: http://superuser.com/questions/66825/what-is-the-difference-between-size-and-size-on-disk Quote: We know that a disk is made up of Tracks and Sectors. In Windows that means the OS allocates space for files in "clusters" or "allocation units". The size of a cluster can vary, but typical ranges are from 512 bytes to 32K or more. For example, on my C:\ drive, the allocation unit is 4096 bytes. This means that Windows will allocate 4096 bytes for any file or portion of a file that is from 1 to 4096 bytes in length. ... Another example would be if I have a file that is 2000 bytes in size. The file size on disk would be 4096 bytes. The reason is, because even though the entire file can fit inside one allocation unit, it still takes up 4096 of space (one allocation unit) on disk (only one file can use an allocation unit and cannot be shared with other files). So the size on disk is the space of all those sectors in which the file is saved. That means, usually, the size on disk is always greater than the actual size. End quote. Suffice to say that when your game/app will be downloaded over the Internet, the amount that needs to be transferred is the size reading that you see in the Build Report Tool, not the size reading on your disk. Side note: Size readings in the Build Report window that have fractional parts are rounded up by two decimal places. === Additional Notes === Don't worry, the assets that the Build Report Tool itself uses won't be included in your build. Copyright © 2013-2014 by Anomalous Underdog For support, you can either: * send me a tweet at http://twitter.com/AnomalusUndrdog * send me a private message in the Unity forums (http://forum.unity3d.com/members/8479-AnomalusUndrdog) * send me an email at anomalous_underdog@yahoo.com

AlphaControls6.21FS 皮肤控件,可用于D5~D2010,BCB6~BCB2009 使用时应编译acnt2010_R.dpk,acnt2010.dpk后再安装 vowstar修改前人的作品,在win7,Delphi2010下编译通过里面的*.obj是zlib,防止编译的时候找不到 AlphaControls :: history 25.02.2009 AlphaControls v6.21 stable released * Improved work of TsMagnifier component, added new SizingMode property :

本课程是商业智能FineBI的应用实践课程，通过对地产行业的部分业务进行整理、然后通过FineBI商业智能系统来梳理准备数据构建多维数据库，然后创建分析... 产品下载地址：http://www.finebi.com/resources/pc-download/

Contents Chapter 1: The Microsoft Developer Studio The Microsoft Developer Studio The Project Workspace Project Workspace Window Project Configurations Managing Complex Projects Project Settings Converting Projects Source Code Files Resource Scripts ResourceView Creating New Resources Identifying Resources Dialog Boxes String Tables Accelerator Tables Menus Icons, Bitmaps and Cursors Version Resources Custom Resources The Visual C++ Compiler Compiling on the Command Line The Foundation Classes MFC Source Code Header Files MFC Libraries Summary Chapter 2: The Wizards and The Gallery AppWizard Starting AppWizard Choosing Your Application's User Interface Selecting Database Support Adding Compound Document Support Embellishing Your User Interface Adding Advanced Features Miscellaneous Options Class Names One More Step Other Application Interfaces Choose Carefully! Compiling Your Application Precompiled Header Files ClassWizard Creating a New Class The .clw File The Browser Browser Files Browsing Shortcuts Components and Controls Gallery Summary Chapter 3: The Application Architecture Hierarchy The Application Framework Generating an Application with AppWizard Understanding the Generated Code CDocument and CView CWinApp CWinThread Locating Threads CCmdTarget Commands for Classes About Message Maps How are Message Maps Created? The BEGIN_MESSAGE_MAP() Macro Inside the Message Map Filling the Holes The END_MESSAGE_MAP() Macro Unfolding the Map There's No Sense of Obligation CObject Memory Management Debugging Support Serialization Run-time Type Information Your Own Classes and CObject The Big Picture: A New Life The WinMain() Function MFC's Message Pump Application Termination Summary Chapter 4: The Document/View Architecture Documents and Views Document/View Designs The Different Views Types of Document Document/View Consciousness What are Document Templates? CSingleDocTemplate S

1,01.zipOutput显示所有的调试信息(5KB)2,02.zipSome general debugging tips一般的调试技巧(11KB)3,03.zipDebugging ISAPI extension调试ISAPI扩展(4KB)4,04.zipLibDump类似DumpBin的工具(10KB)5,05.zipFinding memory leaks发现内存的泄漏(6KB)6,06.zipConvert message ID to a string将消息标志符转换成字符串(4KB)7,07.zipMessage Tracer消息跟踪(5KB)8,08.zipA simple profiler class一个简单的轮廓类(5KB)9,09.zipTerminator中断应用程序(5KB)10,10.zipTranslate Window Style转换窗口风格(5KB)11,11.zipLong String Debugging Macro调试宏(5KB)12,12.zipCheck for loaded DLLs检查装入的动态链接库(4KB)13,13.zipAutoincreasing build number自动增加版本信息的宏(5KB)14,14.zipFile Dialog Macro文件对话框宏(6KB)15,15.zipCode Template add-in for Visual C++ 5.0在VC5中可增加的代码模板(5KB)16,16.zipComment / Uncomment macros命令/反命令宏(5KB)17,17.zipCustom built files自定义生成的文件(5KB)18,18.zipDefine Method定义方法(5KB)19,19.zipExport Makefile输出工程制作文件(5KB)20,20.zipJump to Next/Previous Function Definition跳转到下一个/上一个功能定义(4KB)21,21.zipInverting Assignment Operations转化操作任务(5KB)22,22.zipVC4.2 style keyboard macro recorder for DevStudio 97在DevStudio 97中使用在VC4.2风格的键盘宏记录(4KB)23,23.zipApplication Launcher程序发射器, 能够在Word, Excel, Access, Power Point, Visio和Html中连接网站(6KB)24,24.zipOpen current header file打开当前文件头(7KB)25,25.zipOpen header file打开文件头(4KB)26,26.zipSequentially Renumber Resource ID's重新对资源标识符编号(5KB)27,27.zipA secondary clipboard实现第二个剪贴板, 不过它用的热键是Ctrl+Shift+C, Ctrl+Shift+V和Ctrl+Shift+X(4KB)28,28.zipCase switching这个宏实现文字的大小写互换(4KB)29,29.zipWM_COMMAND user message macroWM_COMMAND用户消息宏(5KB)30,30.zipBetter caret movement by words在IDE中移动快速单词的宏(5KB)

56,678

社区成员

56,708

社区内容

发帖

与我相关

我的任务

社区管理员

加入社区

近7日
近30日
至今

加载中

查看更多榜单

社区公告

暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章