Can anyone help me understand this log?

[s0l0sam]

Hi. I've been having problems with a custom modpack. Can anyone make sense of this log? Any help would be much appreciated.

 

I solved one problem by pasting "javaArguments": "-Dfml.ignorePatchDiscrepancies=true -Dfml.ignoreInvalidMinecraftCertificates=true" in the version.json file, now i get this.

 

[23:42:03] [main/INFO]: Loading tweak class name cpw.mods.fml.common.launcher.FMLTweaker
[23:42:03] [main/INFO]: Using primary tweak class name cpw.mods.fml.common.launcher.FMLTweaker
[23:42:03] [main/INFO]: Calling tweak class cpw.mods.fml.common.launcher.FMLTweaker
[23:42:04] [main/INFO]: Forge Mod Loader version 7.2.217.1147 for Minecraft 1.7.2 loading
[23:42:04] [main/INFO]: Java is Java HotSpot Client VM, version 1.7.0_51, running on Windows 7:x86:6.1, installed at C:Program FilesJavajre7
[23:42:04] [main/WARN]: The coremod mods.battlegear2.coremod.BattlegearLoadingPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft
[23:42:08] [main/WARN]: The coremod codechicken.core.launch.CodeChickenCorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft
[23:42:19] [main/WARN]: The coremod invtweaks.forge.asm.FMLPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft
[23:42:19] [main/WARN]: The coremod codechicken.nei.asm.NEICorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft
[23:42:19] [main/INFO]: Loading tweak class name cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker
[23:42:20] [main/INFO]: Loading tweak class name cpw.mods.fml.common.launcher.FMLDeobfTweaker
[23:42:20] [main/INFO]: Calling tweak class cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker
[23:42:20] [main/INFO]: Calling tweak class cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker
[23:42:20] [main/INFO]: Calling tweak class cpw.mods.fml.relauncher.CoreModManager$FMLPluginWrapper
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class btj (btj) and the actual class. Checksum on disk is 7421feb3, in patch 12c444b4. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class azw (azw) and the actual class. Checksum on disk is 3def5f4b, in patch 43906e90. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class rc (rc) and the actual class. Checksum on disk is 98a3fb6e, in patch e63f8087. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class agm (agm) and the actual class. Checksum on disk is 50a3c97, in patch 6d162948. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class agg (agg) and the actual class. Checksum on disk is 40e035ae, in patch ab1de0c. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class atk (atk) and the actual class. Checksum on disk is a438ea0f, in patch dbb4da1. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class ahu (ahu) and the actual class. Checksum on disk is 782b2e42, in patch 617e5130. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class azz (azz) and the actual class. Checksum on disk is a9265061, in patch 4aa5d796. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class ahr (ahr) and the actual class. Checksum on disk is a7f00dbb, in patch 378dc2fb. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class bll (bll) and the actual class. Checksum on disk is 4cbbd7e8, in patch 59bcd808. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class nd (nd) and the actual class. Checksum on disk is e48bdcf0, in patch c4c0aab0. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class bpn (bpn) and the actual class. Checksum on disk is 704441b9, in patch e178fd81. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class bkg (bkg) and the actual class. Checksum on disk is dfee2ee3, in patch 69e844d1. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class apl (apl) and the actual class. Checksum on disk is 169f27a3, in patch 15f5607a. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class agi (agi) and the actual class. Checksum on disk is b1c4d295, in patch a66c8306. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class xl (xl) and the actual class. Checksum on disk is 798c409b, in patch d1dafa1f. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class bco (bco) and the actual class. Checksum on disk is c1aea6f, in patch 42b8ad71. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class blq (blq) and the actual class. Checksum on disk is fb1408e7, in patch ed15ca0a. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: There is a binary discrepency between the expected input class ate (ate) and the actual class. Checksum on disk is 1f044eb9, in patch 74d375ce. Things are probably about to go very wrong. Did you put something into the jar file?
[23:42:26] [main/ERROR]: FML is going to ignore this error, note that the patch will not be applied, and there is likely to be a malfunctioning behaviour, including not running at all
[23:42:26] [main/ERROR]: Unable to launch
java.lang.RuntimeException: java.lang.NullPointerException
    at cpw.mods.fml.relauncher.CoreModManager$FMLPluginWrapper.injectIntoClassLoader(CoreModManager.java:130) ~[modpack.jar:?]
    at net.minecraft.launchwrapper.Launch.launch(Launch.java:114) [launchwrapper-1.9.jar:?]
    at net.minecraft.launchwrapper.Launch.main(Launch.java:28) [launchwrapper-1.9.jar:?]
Caused by: java.lang.NullPointerException
    at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:192) ~[guava-15.0.jar:?]
    at com.google.common.hash.AbstractByteHasher.putBytes(AbstractByteHasher.java:69) ~[guava-15.0.jar:?]
    at com.google.common.hash.AbstractStreamingHashFunction.hashBytes(AbstractStreamingHashFunction.java:65) ~[guava-15.0.jar:?]
    at cpw.mods.fml.common.patcher.ClassPatchManager.applyPatch(ClassPatchManager.java:95) ~[modpack.jar:?]
    at cpw.mods.fml.common.patcher.ClassPatchManager.getPatchedResource(ClassPatchManager.java:60) ~[modpack.jar:?]
    at cpw.mods.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper.getFieldType(FMLDeobfuscatingRemapper.java:195) ~[modpack.jar:?]
    at cpw.mods.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper.parseField(FMLDeobfuscatingRemapper.java:172) ~[modpack.jar:?]
    at cpw.mods.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper.setup(FMLDeobfuscatingRemapper.java:141) ~[modpack.jar:?]
    at cpw.mods.fml.common.asm.FMLSanityChecker.injectData(FMLSanityChecker.java:179) ~[modpack.jar:?]
    at cpw.mods.fml.relauncher.CoreModManager$FMLPluginWrapper.injectIntoClassLoader(CoreModManager.java:125) ~[modpack.jar:?]
    ... 2 more

Edited August 1, 2014 by s0l0sam

[plowmanplow]

You have not provided sufficient context for the error. When did it happen? What were you doing when it happened? What kind/type of pack were you trying to use? (etc.)

 

I have seen this kind of problem when someone has the wrong version of MC selected in their pack settings or when the contents of a custom modpack were incorrect by having extra files in the bin folder.

 

"Need more input, Stephanie!" - #5

[s0l0sam]

Thank you for the reply, and sorry for the lack of info.

 

The problem was that I had minecraft set to 1.7.4 on the technic site, whereas it was meant to be 1.7.2 ::embarrassed::

 

There was a few more errors after with incompatible mods, but those logs were easy to understand.

 

Thanks again for the help