I got the following error while using freeswitch switch_xml_config.c:78 Could not open curl.conf. This is very interesting, because the offical docs are saying "There is no separate config file for mod_curl.". So is this file needed, yes or no?
I also looked into the source code and found the error being thrown in the following definition, in switch_xml_config: switch_xml_config_parse_module_settings(...). This get's used in mod_curl.c:1072 in do_config(...): switch_xml_config_parse_module_settings("curl.conf", reload, instructions);.
So it looks like mod_curl would like to read a file called "curl.conf".
But as the docs say that there isn't a config file, there is also no info on what this file should contain. Does anyone have any idea what to do? Or should I just create an empty file to suppress the error?
Any hints on what is correct and what to do are appreciated.
I have a curl.conf.xml with the following:
<configuration name="curl.conf" description="cURL module">
<settings>
<param name="max-bytes" value="256000"/>
</settings>
</configuration>
It's in the github repository: https://github.com/signalwire/freeswitch/blob/master/src/mod/applications/mod_curl/conf/autoload_configs/curl.conf.xml
Related
I am facing below issue in my entire installations of M2.
[InvalidArgumentException]
There are no commands defined in the "setup" namespace.
weird thing is I installed fresh Xampp and set up new M2 instance, then also same issue persists. It started coming suddenly and I have tried all available solutions like setting permissions to folders and trying -vvv option and list command to find exact issue.
till now no success. My whole day wasted in debugging this only and now I am running out of thoughts.
If anyone have ideas?
I am using PHP 5.6 and Magento EE 2.1.7
Try Following Solution :
Solution 1 :Please mention setup_version in your module.xml file. Your module.xml file looks like:
<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../../../lib/internal/Magento/Framework/Module/etc/module.xsd">
<module name="Vendor_Module" setup_version="1.0.0"/>
</config>
Solution 2 : You need to give full permission to both var and pub folders recursively.
sudo chmod -R 777 var pub
if above solution not work then try following link
https://magento.stackexchange.com/questions/103774/magento-2-there-are-no-commands-defined-in-the-setup-namespace-on-windows
The reason for this error can be seen in the command output: php -f bin/magento.
This will work for most errors like There are no commands defined in the "..." namespace..
A fairly common cause is an error in xml files e.g. VendorName/ModuleName/etc/config.xml.
I've trying to package up and old MVC 3 project to send it out but I keep getting a strange error where it telling me
'The file '/Views/Shared/print.Master' does not exist. /Views/Questionnaire/View.aspx'
But I can clearly see the file and have renamed it to try and fix it but no luck, then I tried changing the package settings to include everything but that too didn't fix it so does anybody have any idea why this could be happening? (btw it's a 2nd master file)
Any ideas or help would be much appreciated.
Solution was to check file Properties and set 'Build Action' to 'Content'.
i'm using the fsresource sling extension to access the filesystem when working on JSP, JS, CSS and so on. When just yanking the bundle into the crx and configuring it via the OSGi console, everything works as expected. But when i try to add a new runmode (configurtion), the result is unsatisfying.
config/src/main/content/jcr_root/apps/samples/config/org.apache.sling.fsprovider.internal.FsResourceProvider.factory.config.xml
Is the path of the main configuration, which i'm using on a local instance to figure out, how to achieve the desired results, but the best i could get was an unbound configuration displayed in the
system/console/configMgr
The contents of the XML file:
<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0"
xmlns:jcr="http://www.jcp.org/jcr/1.0"
jcr:primaryType="sling:OsgiConfig"
provider.roots="/apps/ui-samples"
provider.file="/Volumes/samples/ui/src/main/content/jcr_root/apps/ui-samples"
provider.checkinterval="1000"/>
Apparently, the i just thought too complicated about the name of the file.
org.apache.sling.fsprovider.internal.FsResourceProvider-samples.xml
for instance does the job.
I was trying to get MZClient to run on OSX 10.7.3 and can't get past the ProviderFactory module not finding any acceptable entries in the /bin directory. I've experimented with trying to hard code the file name, but haven't made it work yet. Any suggestions on how to get this going?
Make sure you have Mono.Zeroconf.Providers.Bonjour.dll in your application directory and also make sure you have Mono.Zeroconf.Providers.Bonjour.dll.config in there with the following contents:
<configuration>
<dllmap dll="dnssd.dll" target="libc.dylib" os="osx" />
</configuration>
It's that .config file that took me awhile to figure out.
For some reason, I can't seem to get CruiseControl.net to checkout code to anywhere but the starteam working folder for a specificed view.
I've tried both overrideViewWorkingDir and overrideFolderWorkingDir, and neither seem to work.
Has anyone been able to do this?
Are you looking for the project's workingDirectory element instead of the starteam override?
<sourcecontrol type="starteam">
<executable>C:\Program Files\starbase\StarTeam 5.4\stcmd.exe</executable>
<project>ProjectName/ViewName</project>
<username>UserName</username>
<password>Password</password>
<host>127.0.0.1</host>
<port>49201</port>
<autoGetSource>true</autoGetSource>
<overrideViewWorkingDir>C:\temp\ProjectName</overrideViewWorkingDir>
</sourcecontrol>
Works fine for me with ccnet 1.4.3 and Startem Cross-Platform Client 2008 R2. Make sure XML is valid. I had overrideViewWorkingDir tag not properly closed and ccnet was ignoring it. Found it by running ccnet.exe from the command line instead of as a service. Also you can use Process Explorer from SysInternals to view command line arguments passed to stcmd.exe
Make sure your working folder properties are set to a relative and not a full path (ex: MyFolder instead of C:\MyProject\MyFolder) or it will override the override. I've seen files checked out to some very odd places in the past when people mistakenly put in full paths when adding a folder to a view.