Summary
When performing an XML Export of a Confluence Space, the export may fail with the following error in the UI:
There was an error in the export. Please check your log files.
:Error creating temp file in folder:
<confluence-home>/temp/xmlexport-<date>/attachments/<pageid>/<attachmentid>See an example of the error below:
Environment
Confluence Server or Data Center running on Linux.
Confluence Home folder mounted on an ext3 or ext4 file system.
Diagnosis
Any export trial of the target Space fails with the same error message in the UI.
The following entries can be found in the atlassian-confluence.log.
Application log entries…
2020-06-17 21:02:37,069 ERROR [Long running task: Export Space] [confluence.importexport.actions.ExportSpaceLongRunningTask] doInTransactionWithoutResult Error during export
-- url: /spaces/doexportspace.action | referer: http://10.125.91.230:8090/spaces/exportspacexml.action?key=SO | traceId: bfffe08bb52b53d2 | userName: admin | action: doexportspace
java.lang.RuntimeException: Error creating temp file in folder: /home/ubuntu/deployments/conf741/confluence-home/temp/xmlexport-20200617-201632-1/attachments/1342429/1342433
at com.atlassian.confluence.pages.persistence.dao.filesystem.FileSystemAttachmentDataUtil.createTempFile(FileSystemAttachmentDataUtil.java:66)
at com.atlassian.confluence.pages.persistence.dao.filesystem.FileSystemAttachmentDataUtil.writeStreamToFile(FileSystemAttachmentDataUtil.java:37)
at com.atlassian.confluence.pages.persistence.dao.FileSystemAttachmentDataDao.writeStreamToFile(FileSystemAttachmentDataDao.java:253)
at com.atlassian.confluence.pages.persistence.dao.FileSystemAttachmentDataDao.saveDataForAttachment(FileSystemAttachmentDataDao.java:240)
at com.atlassian.confluence.pages.persistence.dao.FileSystemAttachmentDataDao.saveDataForAttachment(FileSystemAttachmentDataDao.java:205)
at com.atlassian.confluence.pages.persistence.dao.hibernate.AbstractHibernateAttachmentDao$IntraHibernateAttachmentCopier.saveAttachmentData(AbstractHibernateAttachmentDao.java:869)
at com.atlassian.confluence.pages.persistence.dao.hibernate.AbstractHibernateAttachmentDao$IntraHibernateAttachmentCopier.copy(AbstractHibernateAttachmentDao.java:840)
at com.atlassian.confluence.importexport.impl.FileXmlExporter.backupAttachments(FileXmlExporter.java:160)
at com.atlassian.confluence.importexport.impl.FileXmlExporter.backupEverything(FileXmlExporter.java:99)
at com.atlassian.confluence.importexport.impl.AbstractXmlExporter.doExport(AbstractXmlExporter.java:94)
at com.atlassian.confluence.importexport.impl.FileXmlExporter.doExportInternal(FileXmlExporter.java:60)
at com.atlassian.confluence.importexport.impl.FileXmlExporter.doExport(FileXmlExporter.java:54)
at com.atlassian.confluence.importexport.impl.XmlExporter.doExport(XmlExporter.java:52)
at com.atlassian.confluence.importexport.DefaultImportExportManager.doExport(DefaultImportExportManager.java:212)
at com.atlassian.confluence.importexport.DefaultImportExportManager.exportAs(DefaultImportExportManager.java:178)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:295)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:98)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
at com.sun.proxy.$Proxy291.exportAs(Unknown Source)
at com.atlassian.confluence.importexport.actions.ExportSpaceLongRunningTask$1.doInTransactionWithoutResult(ExportSpaceLongRunningTask.java:95)
at org.springframework.transaction.support.TransactionCallbackWithoutResult.doInTransaction(TransactionCallbackWithoutResult.java:36)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)
at com.atlassian.confluence.importexport.actions.ExportSpaceLongRunningTask.runInternal(ExportSpaceLongRunningTask.java:68)
at com.atlassian.confluence.util.longrunning.ConfluenceAbstractLongRunningTask.run(ConfluenceAbstractLongRunningTask.java:26)
at com.atlassian.confluence.util.longrunning.ManagedTask.run(ManagedTask.java:39)
at com.atlassian.confluence.impl.util.concurrent.ConfluenceExecutors$ThreadLocalContextTaskWrapper.lambda$wrap$1(ConfluenceExecutors.java:90)
at com.atlassian.confluence.vcache.VCacheRequestContextOperations.lambda$doInRequestContext$0(VCacheRequestContextOperations.java:50)
at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContextInternal(VCacheRequestContextManager.java:84)
at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContext(VCacheRequestContextManager.java:68)
at com.atlassian.confluence.vcache.VCacheRequestContextOperations.doInRequestContext(VCacheRequestContextOperations.java:49)
at com.atlassian.confluence.vcache.VCacheRequestContextOperations.lambda$withRequestContext$2(VCacheRequestContextOperations.java:66)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createTempFile(File.java:2024)
at com.atlassian.confluence.pages.persistence.dao.filesystem.FileSystemAttachmentDataUtil.createTempFile(FileSystemAttachmentDataUtil.java:64)
... 43 more
2020-06-17 21:02:37,070 WARN [Long running task: Export Space] [confluence.impl.hibernate.ConfluenceHibernateTransactionManager] doRollback Performing rollback. Transactions:
->[null]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #1534451944)
Showing 10 last transactions at this level out of 223 in total:
[com.atlassian.confluence.upgrade.upgradetask.AttachmentRemoveFileStoreIDsUpgradeTask.getShortDescription]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT,readOnly (Session #2128848446)
[com.atlassian.confluence.upgrade.upgradetask.ContentIndexUpgradeTask.runOnSpaceImport]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #1535240739)
[com.atlassian.confluence.upgrade.upgradetask.ContentIndexUpgradeTask.getBuildNumber]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT,readOnly (Session #1147113303)
[com.atlassian.confluence.upgrade.upgradetask.ContentIndexUpgradeTask.getShortDescription]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT,readOnly (Session #1174478194)
[com.atlassian.confluence.upgrade.upgradetask.attachmentceo.AttachmentContentStatusUpgradeTask.runOnSpaceImport]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #3935704)
[com.atlassian.confluence.upgrade.upgradetask.attachmentceo.AttachmentContentStatusUpgradeTask.getBuildNumber]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT,readOnly (Session #1260967714)
[com.atlassian.confluence.upgrade.upgradetask.attachmentceo.AttachmentContentStatusUpgradeTask.getShortDescription]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT,readOnly (Session #1183342420)
[com.atlassian.confluence.upgrade.upgradetask.EmbeddedCrowdMembershipAggregationUpgradeTask.runOnSpaceImport]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT (Session #472699016)
[com.atlassian.confluence.upgrade.upgradetask.EmbeddedCrowdMembershipAggregationUpgradeTask.getBuildNumber]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT,readOnly (Session #734477673)
[com.atlassian.confluence.upgrade.upgradetask.EmbeddedCrowdMembershipAggregationUpgradeTask.getShortDescription]: PROPAGATION_REQUIRES_NEW,ISOLATION_DEFAULT,readOnly (Session #440486754)
-- url: /spaces/doexportspace.action | referer: http://10.125.91.230:8090/spaces/exportspacexml.action?key=SO | traceId: bfffe08bb52b53d2 | userName: admin | action: doexportspace
2020-06-17 21:02:37,072 ERROR [Long running task: Export Space] [confluence.util.longrunning.ConfluenceAbstractLongRunningTask] run Long running task "Export Space" failed to run.
-- url: /spaces/doexportspace.action | referer: http://10.125.91.230:8090/spaces/exportspacexml.action?key=SO | traceId: bfffe08bb52b53d2 | userName: admin | action: doexportspace
org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only
at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:873)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:710)
at sun.reflect.GeneratedMethodAccessor162.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:205)
at com.sun.proxy.$Proxy213.commit(Unknown Source)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:152)
at com.atlassian.confluence.importexport.actions.ExportSpaceLongRunningTask.runInternal(ExportSpaceLongRunningTask.java:68)
at com.atlassian.confluence.util.longrunning.ConfluenceAbstractLongRunningTask.run(ConfluenceAbstractLongRunningTask.java:26)
at com.atlassian.confluence.util.longrunning.ManagedTask.run(ManagedTask.java:39)
at com.atlassian.confluence.impl.util.concurrent.ConfluenceExecutors$ThreadLocalContextTaskWrapper.lambda$wrap$1(ConfluenceExecutors.java:90)
at com.atlassian.confluence.vcache.VCacheRequestContextOperations.lambda$doInRequestContext$0(VCacheRequestContextOperations.java:50)
at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContextInternal(VCacheRequestContextManager.java:84)
at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContext(VCacheRequestContextManager.java:68)
at com.atlassian.confluence.vcache.VCacheRequestContextOperations.doInRequestContext(VCacheRequestContextOperations.java:49)
at com.atlassian.confluence.vcache.VCacheRequestContextOperations.lambda$withRequestContext$2(VCacheRequestContextOperations.java:66)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2020-06-17 21:02:37,072 WARN [Long running task: Export Space] [confluence.util.profiling.DefaultActivityMonitor] close Exceeded the threshold of 60000 ms: ActivitySnapshot{startTime=1592424992867, threadId=2116, threadName='Long running task: Export Space', userId='', type='long-running-task', summary='Export Space'}
-- url: /spaces/doexportspace.action | referer: http://10.125.91.230:8090/spaces/exportspacexml.action?key=SO | traceId: bfffe08bb52b53d2 | userName: admin | action: doexportspaceAdding DEBUG to the following classes don’t unveil anything different that could be causing an issue.
com.atlassian.confluence.importexport
com.atlassian.confluence.pages.persistence.dao
com.atlassian.hibernate.extras.XMLDatabinderConfluence Home directory is part of an ext3 File System, or ext4 without dir_index and dir_nlink features enabled.
blkidcommand may be helpful to identify the file system type.- tune2fs command may be helpful to identify features enabled on a file system.
If you are reaching the problem described in this KB, there won’t be any other meaningful message in the application logs because of
CONFSERVER-59957
—
Getting issue details…
STATUS
Cause
Some file system types has a limitation on the number of subdirectories as detailed in the below table.
| File system | ext3 | ext4 | GFS | GFS2 | XFS |
|---|---|---|---|---|---|
| Maximum subdirectories | 32,000 |
65,000/unlimited* |
unlimited | unlimited | unlimited |
*ext4 is unlimited when dir_index and dir_nlink features are enabled. |
When exporting a Space, Confluence will copy the attachments from the <confluence-home>/attachments/ver003/ directory structure to <confluence-home>/temp/xmlexport-<date>/attachments/, which is a temporary directory used to store the exported content before compressing in a zip file.
Depending on the number of pages with at least one attachment, Confluence may surpass the maximum number of subdirectories in <confluence-home>/temp/xmlexport-<date>/attachments/.
For example, when <confluence-home> is mounted with an ext3 file system, this limitation is surpassed if the Space has more than 32,000 pages with an attachment each.
Solution
If <confluence-home> is mounted on an ext3 File System, work with internal teams to migrate it to a File System with unlimited support for subdirectories.
If using ext4, make sure dir_index and dir_nlink features are enabled.
If still facing issues while exporting the Space, please contact the support team.
See Also
Hierarchical File System Attachment Storage
Red Hat Enterprise Linux technology capabilities and limits
ext4 — Unlimited number of subdirectories
I need to create a temp file in a specified folder on MAC. However I am able to create the folder at the correct location but not able to create the file inside. I get an error saying it does not have permissions to create the file although i have passed 777 as file permission while creating the folder. please find my code below. I would like to mention that this problem is only on MAC. On windows it executes as expected. please let me know what the issue is.
wxString curDir = SeeWorkingDir() + wxT("Temp\"); //Gets the working directory
if(!wxFileName::DirExists(curDir)) //Checks if directory exists
wxFileName::Mkdir( curDir, 0777, wxPATH_MKDIR_FULL ); // creates the directory
wxString jobcopy = wxFileName::CreateTempFileName(curDir); // should create temp file
asked May 25, 2012 at 10:19
3
I have absolutely no idea what your «SeeWorkingDir()» function is returning, but if it’s returning the application directory then you shouldn’t be writing anything into there.
Why not replace «SeeWorkingDir()» with a path to somewhere on the Macintosh that truly is writable, like the «/tmp/» directory?
answered May 25, 2012 at 10:22
7
You have not explained what your function SeeWorkingDir() does.
Maybe you should use wxFileName::GetTempDir to specify the directory where you store the file. This should be platform independent.
Or, in your call wxFileName::CreateTempFileName(curDir), you could specify the fileTemp parameter to open the file directly.
See the documentation:
wxWidgets 2.8.12 — wxFileName
answered Jun 3, 2012 at 12:49
PauliLPauliL
1,2519 silver badges7 bronze badges
Yesterday, I was trying to install Team Viewer software on my Windows 10 machine.
I downloaded Team Viewer from their official website and then started installing it by double-clicking the application file. However, as soon as I double-clicked the setup file, an error message popped up and said:
I got the same error around a year ago on my Windows 7 machine as well. Fortunately, I knew few methods this time to fix this error.
But, I also thought of writing this article so that it can benefit other users also who are getting the same error.
Why Does Error Writing Temporary File Occur?
First of all, let me make this very clear that this error is not specific to Team Viewer or any other software.
You can get this error while installing any software. It has nothing to do with the software being installed. It’s just some settings in your system that needs to be fixed.
Now coming back to the root cause of this error. Whenever you try to install any software on a Windows machine, it looks for the temp folder to store some data as it writes the registry.
If the temp folder is not set up correctly on your system, this can very well cause error. In such a case, we need to play a bit with the environment variables on our system which you will see shortly.
In the upcoming section, you will get to look at a number of verified methods that can potentially resolve this issue.
Let us get started to implement the methods to get rid of this error. By the end of this section, you should be able to install the software that this causing.
Method 1: Compress The Folder (Workaround)
This is one of the workarounds that has worked very well for most of the users. Since it is easy and less time-consuming, we recommend you implement this method first before trying to implement the other methods. Simply follow the steps given below to implement this workaround:
- Go to the Downloads folder and look for the Installer file that was causing this error.
- Right-click on this file and choose the Send to option.
- This will open another menu. Here, choose the Compressed (Zipped) folder option.
- Your installed file will be zipped inside a folder with the same name.
- Now open this zipped folder.
- Double click on the installer file to start the installation process.
- This should run now without any error. For me, this worked. However, if this workaround is not able to resolve this issue for you, better try the next methods that we listed below. These are much more technical and can resolve this issue once and for all.
Method 2: Check If You Have Correct Environment Variable Set Up
As mentioned above, this error usually occurs when the installer is not able to locate the temp folder on your machine.
How would the installer come to know the exact path of the temp folder? Well, we have some Environment Variables defined in our system. These variables let the installer know the exact path to the temp folder.
Let us, deep-dive, into this method and verify if we have the correct variables defined. If not, we can set them up correctly.
- Right-click on My Computer/ Computer/ This PC depending on the Windows version you are using.
- This will open a Control Panel window. Here, click on the Advanced System Settings option from the left menu.
- Now click on the Environment Variables button.
- Here, you will see all the defined environment variables. You need to check if you have TEMP and TMP environment variables defined exactly as shown in the screenshot below.
- If these are not defined in your system, simply click on the New button and add them one by one.
- Once done, try installing the software that was causing the Error writing temporary file. Hopefully, you should be able to install the software this time.
Method 3: Clean Reboot Your System
The steps listed below will help you in clean rebooting your PC. This can also fix the Error Writing temporary file issue. After implementing these methods, try to install the software that is causing this error and let us know how this method worked for you.
- Go to Control Panel and choose the System and Security link.
- Now select Administrative Tools.
- Double click on the System Configuration option.
- Now choose the Services tab.
- Checkmark Hide all Microsoft services options.
- Now press the Disable all button on the left. Click Apply and OK button.
- Now Restart the system by clicking on the Restart button.
- That’s all. You have clean rebooted your system. Now try installing the software and check if the error still persists.
Method 4: Change The Permission
- Click the Start button and click My Computer.
- Double-click to open drive C.
- Right-click the Windows folder and choose Properties.
- Click to clear the Read-only check box if it is selected.
- Repeat these steps for the TEMP folder and the System folder inside the Windows folder.
- Once these steps are complete, close any open windows and restart the computer.
Method 5: Run “chkdsk” Command
- Open Command Prompt as administrator.
- Enter chkdsk X: /r and press Enter. Be sure to replace X with the letter that matches your hard drive partition that you’re installing the application to. If you’re trying to scan your system partition you’ll have to schedule a restart and scan your partition before Windows 10 starts.
- Now try to run the installation process again.
Final Words
In case of any issues regarding the methods given above, feel free to reach out to us via comments or the Contact Us page. We will try to resolve your issue at the earliest. Stay tuned. Thanks.
Robert Borowski is passionate about blogging and wants to share knowledge with others. His passion, dedication, and quick decision-making quality make him stand from others.
|
0 / 0 / 0 Регистрация: 29.06.2014 Сообщений: 14 |
|
|
1 |
|
|
29.06.2014, 17:31. Показов 28475. Ответов 19
проблемы с временной папкой Temp. начинаю устанавливать программы и выдает эту табличку . Миниатюры
__________________
0 |
|
киберпаразит
9719 / 2783 / 188 Регистрация: 14.06.2011 Сообщений: 9,586 |
|
|
29.06.2014, 17:39 |
2 |
|
прогу от имени админа пробовали ставить?
1 |
|
10931 / 6786 / 1815 Регистрация: 25.12.2012 Сообщений: 28,714 |
|
|
29.06.2014, 18:25 |
3 |
|
1) сколько свободного места на с: (системный, может быть и другим)?
0 |
|
ScrollLock |
|
29.06.2014, 18:54
|
|
Не по теме:
есть папка Temp? мб и есть, но она может быть скрыта (от качества сборки зависит) попадалось, что appdata открыта, а roamingtemp скрыта… вот и думай..
0 |
|
0 / 0 / 0 Регистрация: 29.06.2014 Сообщений: 14 |
|
|
29.06.2014, 19:09 [ТС] |
5 |
|
да есть все папки.
0 |
|
0 / 0 / 0 Регистрация: 29.06.2014 Сообщений: 14 |
|
|
29.06.2014, 19:15 [ТС] |
6 |
|
локальный диск всего один . вот все проверил вроде есть . если кто то может действительно помочь есть вариант выйти в скайп и помочь ? просто из за такой мелочи виндовс менять не хочу да и файлов много важных. антивирус есет смарт нод32 постоянно обновляется вирусов не должно быть . Миниатюры
0 |
|
746 / 648 / 44 Регистрация: 14.05.2011 Сообщений: 1,197 |
|
|
29.06.2014, 20:33 |
7 |
|
начинаю устанавливать программы и выдает эту табличку А экзешники не в папке «Загрузки» какого-либо браузера лежат? Попробуйте переместить файл в другое место, на раб. стол наприм и оттуда устанавливать. Бывает у браузеров случаются заморочки с путями до таких папок.
1 |
|
0 / 0 / 0 Регистрация: 29.06.2014 Сообщений: 14 |
|
|
29.06.2014, 20:38 [ТС] |
8 |
|
нет все равно выдает ошибку
0 |
|
киберпаразит
9719 / 2783 / 188 Регистрация: 14.06.2011 Сообщений: 9,586 |
|
|
30.06.2014, 03:53 |
9 |
|
разрешения на папку temp какие?
1 |
|
0 / 0 / 0 Регистрация: 29.06.2014 Сообщений: 14 |
|
|
30.06.2014, 09:52 [ТС] |
10 |
|
как это ? режим диагностики ? смысле безопасный режим?
0 |
|
киберпаразит
9719 / 2783 / 188 Регистрация: 14.06.2011 Сообщений: 9,586 |
|
|
30.06.2014, 11:50 |
11 |
|
0 |
|
0 / 0 / 0 Регистрация: 29.06.2014 Сообщений: 14 |
|
|
03.07.2014, 10:42 [ТС] |
12 |
|
а к чему ссыка я не понял
0 |
|
киберпаразит
9719 / 2783 / 188 Регистрация: 14.06.2011 Сообщений: 9,586 |
|
|
03.07.2014, 12:42 |
13 |
|
а к чему ссыка к этому:
как это ? режим диагностики ?
0 |
|
0 / 0 / 0 Регистрация: 29.06.2014 Сообщений: 14 |
|
|
03.07.2014, 16:58 [ТС] |
14 |
|
все сделал без результатов.
0 |
|
Модератор
8364 / 3329 / 241 Регистрация: 25.10.2010 Сообщений: 13,538 |
|
|
03.07.2014, 18:39 |
15 |
|
Что за проги пытаетесь установить?
0 |
|
0 / 0 / 0 Регистрация: 29.06.2014 Сообщений: 14 |
|
|
03.07.2014, 20:06 [ТС] |
16 |
|
ПРОБОВАЛ НЕ ПОМОГЛО
0 |
|
киберпаразит
9719 / 2783 / 188 Регистрация: 14.06.2011 Сообщений: 9,586 |
|
|
03.07.2014, 20:12 |
17 |
|
Bers06, а права на users> берс> …… и далее по папкам какие?
0 |
|
0 / 0 / 0 Регистрация: 29.06.2014 Сообщений: 14 |
|
|
06.07.2014, 10:57 [ТС] |
18 |
|
прова администратор , бредмауэр отключал без толку
0 |
|
киберпаразит
9719 / 2783 / 188 Регистрация: 14.06.2011 Сообщений: 9,586 |
|
|
06.07.2014, 13:08 |
19 |
|
причиной может быть имя на кириллице.
Что за проги пытаетесь установить?
0 |
|
1 / 1 / 0 Регистрация: 19.01.2019 Сообщений: 32 |
|
|
07.12.2019, 15:01 |
20 |
|
Скорее всего, вы устанавливали систему на другой диск, когда файлы и папки дистрибутивов уже существовали, существовал неизвестный пользователь из прошлой Винды и т.д.
0 |
На чтение 4 мин. Просмотров 4.2k. Опубликовано 03.09.2019
Как обычно, в основном для новых пользователей, каждый день возникает много сообщений об ошибках и уведомлений, особенно в Windows 10. Это конкретное исправление связано с тем, чтобы помочь вам устранить ошибку, возникшую при попытке создать временный каталог в Windows 10.
Ошибка при попытке создать временный каталог означает, что существует проблема с разрешениями вашей учетной записи пользователя. Эта ошибка обычно отображается с сообщением – невозможно выполнить файлы во временном каталоге.
Эта проблема обычно возникает, когда программное решение устанавливается через исполняемый файл. Когда отображается сообщение об ошибке, вам просто нужно закрыть его, но это не позволит вам продолжить установку. Эта ошибка может возникать в Windows 7, 8 и 10.
Это сообщение об ошибке означает, что ваша система была настроена на блокировку установки. Не нужно паниковать, потому что это только ошибка конфигурации, а не серьезная ошибка. Тем не менее, чтобы вы могли продолжить процесс установки, есть несколько вещей, которые вы можете сделать, чтобы исправить эту ошибку. Ниже приведено несколько методов, которые можно использовать для удаления сообщения об ошибке.
Содержание
- Что делать, если вы не можете создать временный каталог на ПК
- Решение 1. Выберите Запуск от имени администратора.
- Решение 2. Создайте новую папку Temp и измените переменные
- Решение 3: Изменить контроль над папкой TEMP
- Решение 4. Подтвердите включение наследуемых разрешений в папку Temp
Что делать, если вы не можете создать временный каталог на ПК
Решение 1. Выберите Запуск от имени администратора.
Это должно быть очень быстрое решение для вас, если вы спешите завершить установку и у вас нет времени на более обширные решения. Как было сказано ранее, сигнал ошибки означает, что есть проблема с разрешениями.
Это можно легко обойти с помощью этих нескольких шагов:
- Ищите исполняемый файл, который вы хотите установить
-
Щелкните правой кнопкой мыши по нему и в контекстном меню выберите «Запуск от имени администратора».
Это решение должно помочь вам очистить сообщение об ошибке и без проблем установить программное обеспечение.
– СВЯЗАННО: Как открыть временные файлы Интернета в Windows 10
Решение 2. Создайте новую папку Temp и измените переменные
Создание новой папки Temp и изменение переменных – лучший вариант, если сигнал ошибки ясно говорит о наличии проблемы с временным каталогом. Следуйте этим шагам внимательно и уберите ошибку с вашего пути:
- Введите диск C: и создайте новую папку, переименуйте ее в Temp (переключите C: с диска, на котором установлена ваша ОС)
- Нажмите правой кнопкой мыши на Этот компьютер и выберите Свойства в контексте меню.
-
С левой стороны вы увидите ссылку Дополнительные настройки , нажмите на нее
-
Нажмите на вкладку “Дополнительно” в окне и выберите Переменные среды.
- Дважды щелкните TMP в пользовательских переменных
- Значение, которое вы увидите, должно быть % USERPROFILE% AppDataLocalTemp . Измените это на C: Temp. Затем закройте окно, нажав ОК.
В конце концов, попытайтесь установить программу, она должна работать без проблем.
Решение 3: Изменить контроль над папкой TEMP
-
На диске, на котором установлена ваша ОС, введите папку вашего пользователя и найдите папку AppData, в которой вы найдете локальную папку, если ваша ОС установлена в разделе C: и вашим именем пользователя будет User, также адрес в проводнике должно быть указано « C: UsersUserAppDataLocal »
- Найдите папку Temp внутри, щелкните правой кнопкой мыши и выберите в меню свойства.
- В окне свойств нажмите Безопасность .
- В окне безопасности нажмите Все .
- Нажмите «Изменить» и убедитесь, что выбрано все поле «Полный доступ», затем нажмите «ОК» для сохранения.
Это должно дать вам полный доступ к папке Temp и решить проблему с ошибкой 5.
– СВЯЗАННО: Как удалить временные файлы с помощью Очистки диска в Windows 10, 8, 7
Решение 4. Подтвердите включение наследуемых разрешений в папку Temp
Как и в предыдущем решении, выполните следующие действия:
- На диске, на котором установлена ваша ОС, введите папку вашего пользователя и найдите папку AppData, в которой вы найдете локальную папку, если ваша ОС установлена в разделе C: и вашим именем пользователя будет User, также адрес в проводнике должно быть указано «C: UsersUserAppDataLocal»
- Найдите папку Temp внутри, щелкните правой кнопкой мыши и выберите в меню свойства.
- В окне свойств нажмите Безопасность .
-
Нажмите «Дополнительно» для просмотра разрешений.
- В разрешениях должны быть СИСТЕМА, Администратор и Пользователь. Все они должны иметь полный контроль и наследоваться от C: UsersUser
- Найдите «Включить наследуемые разрешения» из родительского выбора этого объекта, нажмите «Продолжить», нажмите «Применить» и затем нажмите «ОК», чтобы сохранить настройку.
К настоящему времени у вас уже должен быть доступ для записи в каталог, который мгновенно исправит эту ошибку.
Обработка разрешений Windows может быть очень сложной для человека, который не знает о нем много. Правильная настройка разрешений поможет вам не допустить серьезного повреждения ОС.
Несмотря на это, эти предложенные решения при правильном использовании позволят вам исправить ошибку невозможности создания временного каталога, встречающегося в Windows 10.
When using the tab bar, I keep getting this error:
bash: cannot create temp file for here-document: No space left on device»
Any ideas?
I have been doing some research, and many people talk about the /tmp file, which might be having some overflow. When I execute df -h I get:
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 9.1G 8.7G 0 100% /
udev 10M 0 10M 0% /dev
tmpfs 618M 8.8M 609M 2% /run
tmpfs 1.6G 0 1.6G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.6G 0 1.6G 0% /sys/fs/cgroup
/dev/sda1 511M 132K 511M 1% /boot/efi
/dev/sda4 1.8T 623G 1.1T 37% /home
tmpfs 309M 4.0K 309M 1% /run/user/116
tmpfs 309M 0 309M 0% /run/user/1000
It looks like the /dev/data directory is about to explode, however if I tip:
$ du -sh /dev/sda2
0 /dev/sda2
It seems it’s empty.
I am new in Debian and I really don’t know how to proceed. I used to typically access this computer via ssh. Besides this problem I have several others with this computer, they might be related, for instance each time I want to enter my user using the GUI (with root it works) I get:
Xsession: warning: unable to write to /tmp: Xsession may exit with an error
Evan Carroll
25.6k37 gold badges143 silver badges253 bronze badges
asked Apr 18, 2016 at 22:07
1
If anyone gets here with this error when their disk isn’t full, be sure to check not just df but also df -i. There are a fixed number of inodes on a filesystem, and every file needs one. If you have just tons of small files, it’s very easy for your filesystem to fill up with these small files while there’s still plenty of space left on the drive when you run df.
answered Nov 26, 2018 at 10:53
5
Your root file system is full and hence your temp dir (/tmp, and /var/tmp for that matter) are also full. A lot of scripts and programs require some space for working files, even lock files. When /tmp is unwriteable bad things happen.
You need to work out how you’ve filled the filesystem up. Typically places this will happen is in /var/log (check that you’re cycling the log files). Or /tmp may be full. There’s many, many other ways that a disk can fill up, however.
du -hs /tmp /var/log
You may wish to re-partition to give /tmp it’s own partition (that’s the old school way of doing it, but if you have plenty of disk it’s fine), or map it into memory (which will make it very fast but start to cause swapping issues if you overdo the temporary files).
Evan Carroll
25.6k37 gold badges143 silver badges253 bronze badges
answered Apr 18, 2016 at 22:48
4
You may also have lost write access to the /tmp/ directory.
It should look like that:
ls -l / |grep tmp
drwxrwxrwt 7 root root 4096 Nov 7 17:17 tmp
You can fix the permissions like that:
chmod a+rwxt /tmp
answered Nov 7, 2016 at 17:38
dothebartdothebart
3512 silver badges4 bronze badges
3
The fastest way to locate your folders that are too full is by narrowing down the folder file size in levels from the root folder.
You start with the root folder by:
sudo du -h --max-depth=1 /
Then — EITHER you increase the depth, i.e. the levels below:
sudo du -h --max-depth=2 /
OR — quicker — you you look which folder has eaten up the most disk space, and do the same on this folder:
sudo du -h --max-depth=1 /home/<user>/<overfull-folder>
Once you found it, just remove that one:
rm -rf <path to overfull-folder>
answered Jun 10, 2018 at 3:47
Agile BeanAgile Bean
2592 silver badges4 bronze badges
2
I was getting error, then I saw
[ 672.995482] EXT4-fs (sda2): Remounting filesystem read-only
[ 672.999802] EXT4-fs error (device sda2): ext4_journal_check_start:60: Detected aborted journal
I was able to confirm this,
mount | grep -i sda2
/dev/sda2 on / type ext4 (ro,relatime,errors=remount-ro,data=ordered)
answered Nov 19, 2017 at 19:36
Evan CarrollEvan Carroll
25.6k37 gold badges143 silver badges253 bronze badges
1
For my case of this same error, it was a cagefs issue as this server was on CloudLinux, addressed with cagefsctl --remount username
answered Oct 30, 2018 at 12:31
If your using Docker:
Just to help any one using docker, just make sure you are deleting the «left over» images from the building process.
To see which images are currently on disk
$ docker images
It will give you a long list and you can start deleting images that you don’t need.
$ docker rmi <image id>.
This should restore your system back to normal.
This is what was causing my problem.
answered May 26, 2021 at 13:09
I was getting the same error. In my case, the disk was filled up by /var/log/syslog and /var/log/kern.log echoing each other in a blizzard of repeated messages, in what was perhaps a kernel panic. 13 G each file. I couldn’t delete or resize in place with sed because I couldn’t even sudo or su -. I had to reboot in recovery mode and drop to a root shell to truncate the files, which I did with sed -i '10001,$ d' /var/log/syslog and sed -i '10001,$ d' /var/log/kern.log (the repeating messages started before the 10000th line in both files).
answered Aug 21, 2021 at 22:20
People have written many things here.
But, I simply emptied the trash bin. It works fine for me now.
rm -rf ~/.local/share/Trash/*
Toby Speight
7,9512 gold badges23 silver badges46 bronze badges
answered Jun 12, 2020 at 8:46
1
Since reboots are very rare on my system , my /tmp had piled up a lot of junk ….Faced this problem recently and cleaned up my /tmp folder.
cd /tmp
sudo rm -rf *
roaima
99.1k14 gold badges126 silver badges239 bronze badges
answered Jun 25, 2020 at 17:34
1
Below thing worked for me.
sudo apt-get autoclean
answered Jul 18, 2020 at 12:40
This is because the disk space is not enough, you need to clean up large files or clean up the process that takes up space:
df -hView hard disk spacedu -sh /*View which directory is the largest, step by step to find large filesdu -h --max-depth=1find the largest file
Kusalananda♦
307k35 gold badges598 silver badges896 bronze badges
answered Jun 10, 2019 at 9:06
1