Categories

  • 631 Topics
    2k Posts
    G
    @Promenade1037 said in i-doit update from 35 to 36 fails with permissions issues: Answering my own question, I reviewed /var/log/messages and found the following entry: "SELinux is preventing /usr/sbin/php-fpm from write access on the directory /var/www/html." Once I disabled SELinux, the update was able to proceed as usual. That is the worst you can do to fix this problem: turn off security. And worse: disable it and not even set it to permissive mode instead. If the SeLinux labels are not correct anymore, fix the SeLinux labels. Do not disable SeLinux. The installer as well as the instructions for the manual installation set the directory to a writable selinux context. So the first question to ask would be why the labels in your installation don't fit anymore?
  • 4k Topics
    16k Posts
    A
    Hello, That's a good question. If your goal is to automate the export of all objects along with their Object IDs, exporting each object type individually can quickly become cumbersome, especially in larger environments. Based on the information you've shared, it would be helpful to know which software version you're using, as export capabilities can vary between releases. In some systems, there may be a global export function, an API endpoint, or a reporting feature that allows you to retrieve multiple object types in a single operation. Unfortunately, if the documentation only describes exports per object type, that may indicate a current limitation of the standard export functionality. I'd be interested to know whether anyone has found a way to perform a complete export of all objects at once, either through a built-in feature, an API, or a scripting workaround. For automation purposes, having a consolidated export including Object IDs would certainly be more efficient than maintaining separate exports for each object category. Looking forward to hearing if someone from the community has experience with this use case.